On Fri, 2003-08-08 at 01:12, Scott Fagg wrote:
> >
> >
> >>>> Nathan Scott <nathans@xxxxxxx> 08/08/2003 3:03:45 PM >>>
> >
> >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.
Do you have some examples of the type of ACL setup you have on these
files?
The problem may well be down in dealing with large numbers of them,
or large sized acls.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@xxxxxxx
|