From: Kristian <kristian@korseby.net>
To: linux-kernel@vger.kernel.org
Subject: massive filesystem corruption with 2.4.9
Date: Tue, 21 Aug 2001 10:00:09 +0200 [thread overview]
Message-ID: <3B821509.8000006@korseby.net> (raw)
Hello.
Since linux-2.4.5 always the same errors occur sporadically after the cold boot
in the morning. (My computer is powered off during the night.) Every second
day I noticed my syslog sais something like the following:
Aug 21 09:01:06 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_new_block:
Allocating block in system zone - block = 3
Aug 21 09:01:06 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: Freeing blocks in system zones - Block = 4, count = 1
Aug 21 09:01:06 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_new_block:
Allocating block in system zone - block = 37
Aug 21 09:01:06 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_new_block:
Allocating block in system zone - block = 45
Aug 21 09:01:07 adlib kernel: mtrr: base(0x42000000) is not aligned on a
size(0x1800000) boundary
Aug 21 09:01:09 adlib last message repeated 2 times
Aug 21 09:01:26 adlib PAM_unix[1929]: (login) session opened for user root by
LOGIN(uid=0)
Aug 21 09:01:26 adlib -- root[1929]: ROOT LOGIN ON tty1
Aug 21 09:01:30 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: Freeing blocks in system zones - Block = 41, count = 4
Aug 21 09:01:30 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_new_block:
Allocating block in system zone - block = 4
Aug 21 09:01:30 adlib kernel: EXT2-fs error (device ide0(3,5)): ext2_new_block:
Allocating block in system zone - block = 7
Aug 21 09:01:30 adlib kernel: EXT2-fs error (device ide0(3,5)):
ext2_free_blocks: Freeing blocks in system zones - Block = 8, count = 2
Today it destroyed my super block and all my root-directories were placed in
/lost+found. I rescued everything with e2fsck-1.14 from a very old rescue-disk
and then again with 1.23, renaming and replacing the directories by hand. A lot
of devices and some .h-files were not recoverable.
These fatal errors are occuring since 2.4.5 (2.4.8 I've not tested.). When I
work with 2.4.4 everything is fine !
I already use the newest version of e2fsck (1.23) and util-linux (2.11f). My
RedHat (Rotkäppchen) 6.2 is rather old, but I don't like gcc 2.96 at all.
I posted this report as the errors occured after a complete crash with 2.4.6
also to the ext2-developers directly but they didn't answered.
Maybe you could help me here ?
Kristian
·· · · reach me :: · ·· ·· · · ·· · ·· · ··· · ·
:: http://www.korseby.net
:: http://www.tomlab.de
kristian@korseby.net ....::
next reply other threads:[~2001-08-21 8:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 8:00 Kristian [this message]
2001-08-21 8:34 ` massive filesystem corruption with 2.4.9 Christian Widmer
2001-08-21 10:14 ` Kristian
[not found] <no.id>
2001-08-21 13:58 ` Alan Cox
2001-08-21 16:00 ` Kristian
2001-08-21 16:18 ` Christian Widmer
2001-08-21 16:23 ` Alan Cox
2001-08-21 19:06 ` Kristian
2001-08-21 16:26 ` Alan Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B821509.8000006@korseby.net \
--to=kristian@korseby.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox