Re: XFS and 2.6.12-rc5

[Nathan Scott <nathans@sgi.com>]

On Fri, Jun 03, 2005 at 10:56:24AM +0200, Goran Gajic wrote:
> >Also, the diagnostic will contain an inode number - for bonus points
> >run "xfs_db -r -c 'inode XXX' -c print /dev/foo" and send me that as
> >well.  Thanks!
> 
> You are right about message here it is:
> 
> xfs_db -r -c 'inode 448631586' -c print /dev/sdb1
> ...
> u.bmx[0-3] = [startoff,startblock,blockcount,extentflag] 
> 0:[177,2557931,341,0] 1:[18014398509481983,4498651825045504,0,1] 
> 2:[15184073051865088,0,0,0] 3:[0,1422,1245184,0]
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^

This is the guy - startblock being zero is fatal.  You'll need to
run xfs_repair to clear that up.  If you know how it got in that
state, I'd be keen to hear it, or if it persists after repair.

[Arun, those superblock checks you added awhile back should be
shutting down the filesystem, not panicing the system, I think?
It looks like theres a signedness issue in the diagnostics too.]

> Turning off cron.daily stops this message so I guess you are right.

Repairing that inode should make it go away entirely.

cheers.

-- 
Nathan