On Dienstag, 6. Januar 2004 15:40, you wrote:
> > > Sounds like the filesystem shut down due to some error, can you check
> > > your logs? In fact checking your logs in general might be useful
> > > here, I wonder if there is anything else going on.
> >
> > One the first machine (server1) I found a sequence of messages like the
> > log attached to this mail. But this message was generated upon startup
> > after powerfail not before. Before the power failure there is nothing xfs
> > related in the logs.
I searched the logs a little deeper. What I overlooked up to now is that close
to the
"XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1596 of file xfs_alloc.c"
line. There are on both servers force shutdown messages. On server1:
Jan 1 12:55:36 server1 kernel: xfs_force_shutdown(device-mapper(254,0),0x8)
called from line 4051 of file xfs_bmap.c. Return address =
Jan 1 12:55:36 server1 kernel: Filesystem "device-mapper(254,0)": Corruption
of in-memory data detected. Shutting down filesystem: device-mapper(254,0)
Jan 1 12:55:36 server1 kernel: Please umount the filesystem, and rectify the
problem(s)
On server2:
xfs_force_shutdown(device-mapper(254,3),0x8) called from line 4051 of file
xfs_bmap.c. Return address =0xc4f6ff8b
Jan 2 00:41:43 server2 kernel: Filesystem "device-mapper(254,3)": Corruption
of in-memory data detected. Shutting down filesystem: device-mapper(254,3)
Jan 2 00:41:43 server2 kernel: Please umount the filesystem, and rectify the
problem(s)
This was past midnight, so I guess energy went away and then came back again
and went away once again. My reboot was on the same day at about 1:00 Uhr pm.
Perhaps many errors I see in the syslog like:
Jan 1 13:05:35 server1 kernel: XFS internal error XFS_WANT_CORRUPTED_RETURN
at line 302 of file xfs_alloc.c. Caller 0xc4f027d0
Jan 1 13:05:35 server1 kernel: c63bf820 c4f01c33 c4f88c75 00000001 00000000
c4f88c69 0000012e c4f027d0
Jan 1 13:05:35 server1 kernel: 00000000 00000000 00000000 00000000
00000010 c63bf9dc c4e77e8c c63bf8cc
were caused by my attempts to mount the "forced down" filesystem which failed.
The time could be right but I cannot remember exactly when I tried to mount
the failed devices before I started xfs_repair. So I am not sure about this.
> Can you put your xfs_repair binary there as well?
Its there: http://www.uni-koblenz.de/~krienke/xfs/xfs_repair.gz
I also put xfs_alloc.c and xfs_bmap.c from "my" kernel-source there:
http://www.uni-koblenz.de/~krienke/xfs/xfs_alloc.c.gz
http://www.uni-koblenz.de/~krienke/xfs/xfs_bmap.c.gz
Thanks a lot
Rainer
--
---------------------------------------------------------------------------
Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022
Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312
Mail: krienke@xxxxxxxxxxxxxx, Web: http://www.uni-koblenz.de/~krienke
Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html
---------------------------------------------------------------------------
pgpXzHyLfLOkj.pgp
Description: signature
|