Re: XFS shutdown with 1.3.0
Simon Matter <simon.matter <at> ch.sauter-bc.com>
2003-09-02 11:14:23 GMT
>> xfs_inotobp: xfs_imap() returned an error 22 on md(9,8). Returning
>> error.
>> xfs_iunlink_remove: xfs_inotobp() returned an error 22 on md(9,8).
>> Returning error.
>> xfs_inactive: xfs_ifree() returned an error = 22 on md(9,8)
>> xfs_force_shutdown(md(9,8),0x1) called from line 1846 of file
>> xfs_vnodeops.c. Return address = 0xd08bd8c6
>> Filesystem "md(9,8)": I/O Error Detected. Shutting down filesystem:
>> md(9,8)
>> Please umount the filesystem, and rectify the problem(s)
>
> Hmmm - seen a couple of these reports now, unfortunately I haven't
> come across it myself yet. Someone else has a bugzilla bug open,
> it seems to be really difficult to trigger this one.
>
The only thing I did in that moment was removing a file of ~1.5G size with
rm file. Although there were some files open on this filesystem via NFS,
there was absolutely no activity.
>>
>> [root <at> xxl root]# xfs_check /dev/md8
>> xfs_check: warning - cannot get sector size from block device /dev/md8:
>> Invalid argument
> ^^^^^^^^^^^^^^^^^^^
> this is where those bogus md "ictls" are coming from, btw. Its
> fixed in more recent kernels, you can search lkml archives for
> recent Neil Brown patches and find the fix (its some missing code
> in md, and is harmless here).
(Continue reading)