Simon Matter wrote:
> I've been running cyrus-imapd servers on XFS for years now without any
> problems related to XFS. I also had the sig11 and die problem but it never
> affected XFS, and I think it really should not.
I agree - a non root userland process should definitely not affect the
filesystem. I mentioned it only because it may be a reason for a
non-expected pattern of fs operations.
>>Last week, I get this:-
>>
>>xfs_inotobp: xfs_imap() returned an error 22 on sd (8,8). Returning error.
>>xfs_iunlink_remove: xfs_inotobp() returned an error 22 on sd (8,8).
>>Returning an error.
>>xfs_inactive: 0xfs_ifree() error 22 on sd (8,8)
>>xfs_force_shutdown: (sd(8,8)0x1) called from line 1873 of file
>>xfs_vnodeops.c
>> Return address = 0x01ef8ba
>>File system sd (8,8): I/O error detected.
>
> ^^^^^^^^^
> I'm not an expert for those error messages but I guess it unfortunately a
> hardware error, isn't it? Did you check dmesg output when this happened?
That was the dmesg output - not much goes to logs, as they're on /var,
which was the affected filesystem. Things I've seen suggest that this
error can certainly be caused by a hardware problem, but the disk is a
hardware RAID5 array on an ICP controller, which maintains it's own
hardware log of disk problems. I've seen no sign of any problems with
the array, and the controller doesn't show anything that could have
presented an error to the OS layer, so I'm inclined to doubt the
"hardware error" theory at the moment.
Mike.
|