All of lore.kernel.org
 help / color / mirror / Atom feed
From: david <david@blue-labs.org>
To: Tony Hoyle <tmh@magenta-netlogic.com>
Cc: jason <jason@lacan.dabney.caltech.edu>, linux-kernel@vger.kernel.org
Subject: Re: kernel panic with 2.4.x and reiserfs
Date: Fri, 27 Apr 2001 20:22:36 -0700	[thread overview]
Message-ID: <3AEA377C.8090005@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10104270104010.7570-100000@lacan.dabney.caltech.edu> <3AE9913B.6090208@magenta-netlogic.com>

To your complaint, I have to add my kudos.  I frequently run into 
crashes and I have only had reiserfs filesystem that I had to rebuild in 
well over a year of using it on half a dozen workstations.  I use 2.4 
exclusively and have often had "premature restarts".

David

Tony Hoyle wrote:

> 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
>




      parent reply	other threads:[~2001-04-28  3:23 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
2001-04-27 16:08   ` Chris Mason
2001-04-28  3:22   ` david [this message]

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=3AEA377C.8090005@blue-labs.org \
    --to=david@blue-labs.org \
    --cc=jason@lacan.dabney.caltech.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmh@magenta-netlogic.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.