xfs
[Top] [All Lists]

Re: XFS pseudo OOPs.

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: XFS pseudo OOPs.
From: Dan Yocum <yocum@xxxxxxxx>
Date: Tue, 16 Mar 2004 07:51:07 -0600
Cc: xfs-list <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20040316055036.GA2067@frodo>
Organization: Fermilab
References: <4055EA33.5030608@fnal.gov> <20040316055036.GA2067@frodo>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031016
Nathan,

If an md device decided to go wonko would that make it look like a FS 
corruption?  For instance, these FSs are RAID50 (hw raid5, sw raid0) across 
3 volumes.  I got to thinking about the kernel I've been using from ATrpms 
and I know he added an LVM patch.  I haven't looked at it, yet, but maybe it 
touches something in the kernel that md doesn't like.  Also, now that I'm 
back to my old standby kernel (2.4.18-26 + XFS v1.2) I'm not getting these 
errors/traces.

Thoughts?

Thanks,
Dan

Nathan Scott wrote:
> On Mon, Mar 15, 2004 at 11:38:59AM -0600, Dan Yocum wrote:
> 
>>I don't know, yet, if this is a hardware or a software problem.  I'm trying 
>>to figure that out.
>>
>>I'm using the ATRpms kernel (2.4.20-30_37 w XFSv1.3.0 et al. see the list at 
>>http://atrpms.physik.fu-berlin.de/dist/rh73/kernel/ ) and I'm getting these 
>>errors and sometimes it forces the FS offline or makes the system unusable - 
>>not really a freeze, but you can't interrupt it.
>>
>>Mar  1 14:21:25 sdssdp37 kernel: Filesystem "md(9,3)": XFS internal error 
>>xfs_btree_check_sblock at line 341 of file xfs_btree.c.  Caller 0xf886c543 ...
>>...
>>Trace; f88566df <[xfs]xfs_btree_check_sblock+9f/c0>
>>Trace; f88b4778 <[xfs].rodata.end+6179/14461>
>>Trace; f88b473b <[xfs].rodata.end+613c/14461>
>>Trace; f8841909 <[xfs]xfs_alloc_increment+159/180>
>>Trace; f8841909 <[xfs]xfs_alloc_increment+159/180>
>>Trace; f885667f <[xfs]xfs_btree_check_sblock+3f/c0>
>>Trace; f88405e9 <[xfs]xfs_alloc_lookup+289/350>
>>Trace; f883d60a <[xfs]xfs_alloc_ag_vextent_size+4a/440>
> 
> 
> Hi Dan,
> 
> Looks like you've got filesystem corruption, from your trace it
> looks like its in one of the freespace btrees in an AG header.
> Its difficult to diagnose whether this is caused by a hardware
> or software failure - if you can find a pattern or better yet a
> reproducible test case, that'd help us alot in figuring it out.
> The output from xfs_repair may provide us additional clues also.
> 
> thanks.
> 

-- 
Dan Yocum
Sloan Digital Sky Survey, Fermilab  630.840.6509
yocum@xxxxxxxx, http://www.sdss.org
SDSS.  Mapping the Universe.  There is no spoon.


<Prev in Thread] Current Thread [Next in Thread>