From: Oleg Drokin <green@namesys.com>
To: "Henning P. Schmiedehausen" <hps@intermeta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiserfs bug
Date: Thu, 28 Nov 2002 13:03:08 +0300 [thread overview]
Message-ID: <20021128130308.A11579@namesys.com> (raw)
In-Reply-To: <as4mo7$ae8$1@forge.intermeta.de>
Hello!
On Thu, Nov 28, 2002 at 09:13:43AM +0000, Henning P. Schmiedehausen wrote:
> >Sorry, but you seems to have faulty hardware (bad harddrive or something).
> >Reiserfs cannot tolerate bad blocks in journal area right now.
> >I'd suggest you to make a backup of your device and then to replace bad
> >harddrive.
> You still shouldn't panic the kernel in this case. IMHO.
Sure, panicking the kernel in case of a write error is not very nice thing to
do.
Jeff Mahoney (of SuSE) is working on improving this situation. He even
released a preview patch some time ago (on 7th May).
Bye,
Oleg
next prev parent reply other threads:[~2002-11-28 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-28 8:28 reiserfs bug Sönke Ruempler
2002-11-28 8:47 ` Oleg Drokin
2002-11-28 8:50 ` Sonke Ruempler
2002-11-28 8:57 ` Oleg Drokin
2002-11-28 9:04 ` Sonke Ruempler
2002-11-28 9:09 ` Oleg Drokin
2002-11-28 9:12 ` Sonke Ruempler
2002-11-28 9:13 ` Henning P. Schmiedehausen
2002-11-28 10:03 ` Oleg Drokin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-22 23:26 Pablo Barbáchano
2005-01-23 11:13 ` Pablo Barbáchano
2004-07-01 6:09 Hongwei Li
2004-07-01 20:44 ` Oleg Drokin
2004-10-05 15:01 ` Vladimir Saveliev
2001-10-08 16:44 ReiserFS Bug Aleksander Adamowski
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=20021128130308.A11579@namesys.com \
--to=green@namesys.com \
--cc=hps@intermeta.de \
--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