We are running Suse SLES8 2.4.21-138 kernel with XFS 1.3.
We see the following XFS crash in our syslog.
kernel: xfs_inotobp: xfs_imap() returned an error 22 on lvm(58,0). Returning
kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on lvm(58,0).
kernel: xfs_inactive:^Ixfs_ifree() returned an error = 22 on lvm(58,0)
kernel: xfs_force_shutdown(lvm(58,0),0x1) called from line 1866 of file
address = 0xc020941b
kernel: Filesystem "lvm(58,0)": I/O Error Detected. Shutting down filesystem:
kernel: Please umount the filesystem, and rectify the problem(s)
Here are the steps we used to reproduce the problem.
1. Creare 3 RAID 5 sets.
2. Group these 3 RAID sets to one large physical volume
3. Create an XFS file system on it
4. Run dbench -c ./client.txt 64
5. Within 10 minutes the file system crashes.
Having dropped in to KDB I see that the problem occur in xfs_iunlink_remove()
I think it is expected that the unlinked inode number be either in the
array or if not xfs_dinode_t->di_next_unlinked list ( first item has the
array). How ever in this case the xfs_dinode_t->di_nlink is 0 and the
agi_unlinked array is filled
up with 0xFFFFFFFF or I gather NULLAGINO. The agi seem to be sensible judging
from the Magic
number. So it seem that some inode got escaped from the unlink process. How
that would happen
is beyond me. Any insights would be very helpful.
The problem seem to be very similar to
Thanks in advance.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around