From: Tony Hoyle <tmh@magenta-netlogic.com>
To: jason <jason@lacan.dabney.caltech.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel panic with 2.4.x and reiserfs
Date: Fri, 27 Apr 2001 16:33:15 +0100 [thread overview]
Message-ID: <3AE9913B.6090208@magenta-netlogic.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10104270104010.7570-100000@lacan.dabney.caltech.edu>
jason wrote:
> Hello,
>
> As the subject would imply, I've been having problems with 2.4.x. I have
> my root partition (/dev/hda1) as reiserfs and also have another harddrive
> with a reiserfs partition (/dev/hdc1). Several programs write (e.g. save
> files to) /dev/hdc1, and I also store files there. Under 2.4.2, whenever
> manually copying files from hda1 to hdc1, I would get a kernel panic, the
Reiserfs doesn't cope well with crashes.... Under 2.4 I wouldn't
recommend using it on any kind of critical server - it seems to
progressively corrupt itself (I'm looking at the second reformat and
reinstall in a week, and I'm not a happy bunny).
As the warning on reiserfsck says, the rebuild-tree option is a last
resort. It's as likely to make the problem worse then improve it (It
rounds all the file lengths up to a block size, padding with zeros,
which breaks lots of stuff). Backup what you can first.
I find that if you run reiserfsck -x /dev/hda1 a couple of dozen times
it slowly fixes stuff that it couldn't fix on the previous pass.One
thing that can't fix is the bug that seems to make random files on the
FS unreadable even for root.The only way I've found around that one is a
periodic format/reinstall.
Tony
--
Where a calculator on the ENIAC is equpped with 18,000 vaccuum
tubes and weighs 30 tons, computers in the future may have only
1,000 vaccuum tubes and perhaps weigh 1 1\2 tons.
-- Popular Mechanics, March 1949
tmh@magenta-netlogic.com
next prev parent reply other threads:[~2001-04-27 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 9:40 kernel panic with 2.4.x and reiserfs jason
2001-04-27 14:24 ` Chris Mason
2001-04-27 15:33 ` Tony Hoyle [this message]
2001-04-27 16:08 ` Chris Mason
2001-04-28 3:22 ` david
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=3AE9913B.6090208@magenta-netlogic.com \
--to=tmh@magenta-netlogic.com \
--cc=jason@lacan.dabney.caltech.edu \
--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