This has been lurking since January, I suspect a number of
people have had recovery failures because of it. If you crashed
with a lot of deleted files, this bug would lead to a filesystem
shutdown during recovery.
You would probably have seen something like this:
XFS mounting filesystem ide0(3,3)
Starting XFS recovery on filesystem: ide0(3,3) (dev: 3/3)
xfs_inotobp: xfs_imap() returned an error 22 on ide0(3,3). Returning error.
xfs_iunlink_remove: xfs_inotobp() returned an error 22 on ide0(3,3).
Returning error.
xfs_inactive: xfs_ifree() returned an error = 22 on ide0(3,3)
xfs_force_shutdown(ide0(3,3),0x1) called from line 1903 of file xfs_vnodeops.c.
Return address = 0xc01d61a1
I/O Error Detected. Shutting down filesystem: ide0(3,3)
Please umount the filesystem, and rectify the problem(s)
Ending XFS recovery on filesystem: ide0(3,3) (dev: 3/3)
Steve
Date: Thu Aug 29 14:26:29 PDT 2002
Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4
The following file(s) were checked into:
bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs
Modid: 2.4.x-xfs:slinx:126410a
linux/fs/xfs/xfs_log_recover.c - 1.240
- when processing unlinked inodes and dealing with the di_next_unlinked
field, endian flip it.
|