From: Oleg Drokin <green@namesys.com>
To: Sonke Ruempler <ruempler@topconcepts.com>
Cc: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com
Subject: Re: reiserfs bug
Date: Thu, 28 Nov 2002 12:09:59 +0300 [thread overview]
Message-ID: <20021128120959.A2904@namesys.com> (raw)
In-Reply-To: <079a01c296bd$1d51f150$6600a8c0@topconcepts.net>
Hello!
On Thu, Nov 28, 2002 at 10:04:10AM +0100, Sonke Ruempler 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.
> umm, that are originally freecom 20gig ide hdds in a firewire-case, i
> replaced the hdds with 120gig maxtor hdds and they worked for 2 weeks until
> today.
> maybe the firewire<->ide converter is corrupted?
I do not know. Your log indicates that your scsi subsystem encountered errors.
But I do not know actual source of errors. May be if you enable more verbose
scsi errors reporting it will give you some clue. (like what command
failed, what was the error code and this kind of stuff).
Bye,
Oleg
next prev parent reply other threads:[~2002-11-28 9:02 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 [this message]
2002-11-28 9:12 ` Sonke Ruempler
2002-11-28 9:13 ` Henning P. Schmiedehausen
2002-11-28 10:03 ` Oleg Drokin
-- 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=20021128120959.A2904@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=ruempler@topconcepts.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox