* 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
> 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:
Jul 31 12:52:51 nope kernel: Please umount the filesystem, and rectify the
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.
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.
PS: egcs-1.1.2 and all that funky approved-by-Steve devel stuff.
.+'''+. .+'''+. .+'''+. .+'''+. .+''
Kelemen Péter / \ / \ Peter.Kelemen@xxxxxxx
.+' `+...+' `+...+' `+...+' `+...+'