xfs
[Top] [All Lists]

Re: xfs_iget...

To: Daniel Moore <dxm@xxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: xfs_iget...
From: Steve Lord <lord@xxxxxxx>
Date: Mon, 28 Aug 2000 14:18:08 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Message from Daniel Moore <dxm@clouds.melbourne.sgi.com> of "Mon, 21 Aug 2000 11:57:26 +1000." <200008210157.LAA64653@clouds.melbourne.sgi.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
> 
> Re: the xfs_iget bug, could the people who've seen it please
> post some more info. I'd like to post this bug and need some more
> details on the symptons etc.
> 
> I'm seeing "bad inode magic/vsn daddr" messages from xfs_itobp
> and I'm wondering if these are connected.
> 
> Steve, do you think this is connected to pv 797419?
> 
> Ta
> -----------------------------------------------------
>  Daniel Moore                  dxm@xxxxxxx
>  R&D Software Engineer         Phone: +61-3-98348209
>  SGI Performance Tools Group   Fax:   +61-3-98132378
> -----------------------------------------------------


I suspect what you are seeing is due to running fsstress - it exercises
the bulkstat interface asking for random inode numbers - which in all
probability do not exist. It calculates a disk location based on the inode
number and reads the block into memory - it fails these checks if it is
not a real inode block and you get the error message.

Irix exhibits exactly the same behavior with fsstress, this one is not a
bug it is a feature of the test program.

Steve




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