hi Marcin -
Looks like you hit a couple of bugs. :)
_something_ caused a forced shutdown on your filesystem, and there was a
bug in xfs around Jan 3 which would write data to block zero after a
forced shutdown - and that's where your superblock lives. Actually, it
overwrote the first 4k, so there's a bit more important FS data there...
The good news is this forced shutdown bug is fixed in CVS now, so if you
shut down again, your filesystem should be happier. The bigger question
is, why did your filesystem shut down...
Jan 12 18:20:02 piaskowy kernel: cmn_err level 1 Filesystem "ide0(3,2)":
xfs_iflush: Bad inode 70394 magic number 0xb062, ptr 0xcc20aa00
Jan 12 18:20:02 piaskowy kernel: xfs_force_shutdown(ide0(3,2),0x8)
called from line 3064 of file xfs_inode.c. Return address = 0xc01a82f2
Jan 12 18:20:02 piaskowy kernel: Fatal error on root filesystem
Jan 12 18:20:02 piaskowy kernel: Corruption of in-memory data detected.
Shutting down filesystem: ide0(3,2)
Those are the details, but it's not clear what the cause may be.
-Eric
On Tue, 2002-02-05 at 16:08, Marcin Zieba wrote:
> Hi,
> I'm running Linux piaskowy 2.4.17-xfs #1 Thu Jan 3 13:53:36 CET 2002
> i586 unknown, compiled with gcc 2.95.4 (Debian Sid)
> and my partition /home, where /var is symlinked (it's my workstation,
> and on /home i've got plenty of space), disappeared, second time in a
> month, so i think, it looks like repeatable bug. (due to /var on /home,
> i don't have much logs..)
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|