Filesystem Shutdown due to Error 22

Federico Sevilla III
2006-07-30T03:53:22Z

Hi,

I am running Linux 2.6.17.7 on a Debian GNU/Linux Sarge machine
(xfsprogs 2.6.20 and xfsdump 2.2.27). I was hit recently by the dir2
corruption problem, but already fixed this using the procedure in the
FAQ after upgrading the kernel.

I have a weekly scheduled task that runs xfs_fsr and this morning found
that my server's filesystem (the same one previously hit by the dir2
issue) had been shut down. I don't have console access to this server
but managed to get the following off the logs which are on a separate
filesystem:

kernel: xfs_inotobp: xfs_imap() returned an error 22 on md1. Returning error.
kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on md1. Returning error.
kernel: xfs_inactive:^Ixfs_ifree() returned an error = 22 on md1
kernel: xfs_force_shutdown(md1,0x1) called from line 1763 of file fs/xfs/xfs_vnodeops.c. Return address = 0xc01fa80c

I ran xfs_repair, and found 20 disconnected inodes of which 16 are
filled with nulls. No other problems were found with the filesystem.

I have an identical server (hardware, kernel and core utilities, albeit
different applications) which went through the same upgrade path and
dir2 corruption, but went through today's xfs_fsr without any problems.

Any clues as to what's causing this?

Cheers!

--> Jijo

--
Federico Vicente C. Sevilla III
Information Technology Consultant
Q Software Research Corporation
Website: http://jijo.free.net.ph