At 22:16 31-7-2001 +0200, Peter.Kelemen@xxxxxxx wrote:
* Ralf G. R. Bergs (rabe@xxxxxxxxxxxxxx) [20010731 20:50]:
> Jul 31 14:06:43 server kernel: xfs_force_shutdown(sd(8,5),0x1) called from
> line 1013 of file xfs_trans.c. Return address = 0xcc8e71b3
> Jul 31 14:06:43 server kernel: I/O Error Detected. Shutting down
filesystem:
> sd (8,5)
> Jul 31 14:06:43 server kernel: Please umount the filesystem, and
rectify the
> problem(s)
> Do you have any idea what could be causing this? Or any hints
> how to further investigate the problem?
Linux nope 2.4.7-xfs #1 Sun Jul 22 14:59:11 CEST 2001 i686 unknown
Not much, but I experienced a similar event with very light load
today, running CVS 2.4.7 as of 2001/07/22:
Jul 31 12:52:51 nope kernel: xfs_force_shutdown(lvm(58,0),0x1) called from
line
4069 of file xfs_bmap.c. Return address = 0xc01863ab
Jul 31 12:52:51 nope kernel: Fatal error on root filesystem
Jul 31 12:52:51 nope kernel: I/O Error Detected. Shutting down filesystem:
lvm(58,0)
Jul 31 12:52:51 nope kernel: Please umount the filesystem, and rectify the
problem(s)
I upgraded couple of Debian packages while running X, then this
error occured, forcing me to reboot. xfs_repair complained about
inodes not belonging to any files. Some of my shared libs turned
into collection of binary zeroes, my /etc/inetd.conf got linked
(!) to /lib/libkdb.so.1 (and yes, I have *never* had a file with
that name -- weird?!). Otherwise everything seems to be intact.
That is probably caused by an IO error. I see you are using lvm which could
be related.
If an IO error occurs the filesystem will shutdown to prevent more damage.
This error could be on the device (bad cluster on the disk) or something in
a software layer like md or lvm going wrong which is seen by XFS as a
hardware error.
What is actually the lvm device. Do you use md or any other software that
might interfere?
IDE or scsi and what controller and system. How is the lvm device constructed.
Sorry for not being able to provide more exact debugging terms and
not preserving the damaged filesystem, but I had to come around
this as it actually was my workstation's root filesystem.
Ah, yes. You tried to actually "work" on a "workstation"? :-)
Cheers
--
Seth
Every program has two purposes one for which
it was written and another for which it wasn't
I use the last kind.
|