Re: kernel errors when XFS filesystem fills up

["Scott Fagg" <scott.fagg@arup.com>]

>
>
>>>> Nathan Scott <nathans@sgi.com> 08/08/2003 3:03:45 PM >>>
>On Fri, Aug 08, 2003 at 02:33:52PM +1000, Scott Fagg wrote:
>> 
>> /proc/sys/fs/xfs/error_level is set to 3 on the box in question.
><snip>
>
>You are doing a permissions check on an inode with an ACL.  The
>extended attribute part of the inode is in btree or node format,
>hence we're down in xfs_da_do_buf (da= dir/attr) reading in the
>extended attribute data.

That sounds reasonable. Sometimes the error is triggered during a find, if it hits
the inode in question.

Sometimes there are subtle variations in the stack trace, in terms of
the function names. I'll find some old logs and get some samples.

>
>For some strange reason we are trying to read at AG blk 0 for that
>inode, which is wrong - block zero in an AG holds the SB/AGF/AGI/
>AGFL for that allocation group.  Its not clear if this is due to
>the EA data on disk pointing to that block, or a bug in the kernel
>code.  The tools not finding anything suggests to me a kernel bug,
>not sure where though...
>

So what should i do to generate more debug info ?

Not sure if it helps, but this sequence of events might give a clue :

- run 'find' on the XFS vol
- it hits a nasty inode and trigges the kernel message i see.
- track down the inode mentioned and remove it and it's parent directory
- run 'find' again .. no errors triggered
- copy heaps of files back to the XFS vol and the error will probably occur again a couple of times, even if i'm copying 1000's of files.
- backup files ( except faulty inodes )
- re-format XFS parition
- copy files back
- .. no errors occur .. until the volume fills up again.

That help ? 


>cheers.
>
>-- 
>Nathan
>
>