* Martin Michlmayr <[EMAIL PROTECTED]> [20070316 21:24]:

> I just found http://oss.sgi.com/archives/xfs/2007-03/msg00078.html
> which is another XFS problem on NSLU2.  Apparently it's because of a
> miscompilation in XFS on ARM.  I'll confirm with the XFS developers
> whether your problem may be caused by this too after reproducing it on
> another ARM machine, hopefully this weekend.

ACK, I was talking to Eric Sandeen on #xfs and we played around with
stuff like 'xfs_db -r /dev/... => sb 0; p', xfs_check,... and came
to the same conclusion.

I've the log from xfs_repair available, JFTR:

# xfs_repair -n /dev/sdb2
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
entry "                                                " in shortform directory 
128 references invalid inode 1852205415
size of entry #0 overflows space left in in shortform dir 128
would junk 4 entries
would have corrected entry count in directory 128 from 4 to 0
would have corrected directory 128 size from 59 to 8
would have corrected root directory 128 .. entry from 8390144 to 128
entry "                                                " in shortform directory 
131 references invalid inode 3619769856
size of entry #0 overflows space left in in shortform dir 131
would junk 4 entries
would have corrected entry count in directory 131 from 4 to 0
would have corrected directory 131 size from 67 to 8
[...]

regards,
-mika-

Attachment: pgpQiBcfmXiUH.pgp
Description: PGP signature

Reply via email to