At 12:34 1-8-2001 +0200, angus wrote:
I had one problem with a linux box in xFS.
This box is in IDE (no VIA or other buggy chipset),
no RAID SOFT or LVM.
This is the dmesg output:
xfs_force_shutdown(ide0(3,8),0x1) called from line 4069 of file
xfs_bmap.c. Return address = 0xc017fbcb
I/O Error Detected. Shutting down filesystem: ide0(3,8)
Please umount the filesystem, and rectify the problem(s)
This is error is common when XFS runs into IO error. It is there to protect
your data. Since in your case there is nothing in between the disk and the
fs layer I suspect that you have run into a bad cluster on your disk.
This is not always fatal since in some cases the newer IDE drives will map
a bad cluster out to a new one that is spare. This will be done untill all
spare clusters inside the disk are gone and then will produce errors.
Note: If you have S.M.A.R.T. you can be notified when a drive is going bad.
This does not always work right since some disks will only start reporting
errors when all the spare clusters are gone while others start barking
loudly and give warnings when it starts mapping out bad clusters in the
first place. Each disks manufacturer behaves different.
What also can happen is that a bad cluster is detected but it is not
restored untill the first powercycle/reboot. This is something that has
been observed but should not happen. It's a very rare case. Maybe the folks
at linux-ide.org can tell you something more.
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.