From: Oleg Drokin <green@namesys.com>
To: ted@psyber.com, linux-kernel@vger.kernel.org,
Hans Reiser <reiser@namesys.com>
Subject: Re: New IDE code and DMA failures
Date: Thu, 11 Apr 2002 18:10:27 +0400 [thread overview]
Message-ID: <20020411181027.A1870@namesys.com> (raw)
In-Reply-To: <200204111236.g3BCaMX10247@Port.imtp.ilyichevsk.odessa.ua> <20020411130544.GA8163@dondra.ofc.psyber.com>
Hello!
On Thu, Apr 11, 2002 at 06:05:44AM -0700, Ted Deppner wrote:
> In one of my tests the contents /dev/hdh was additionally corrupted (a
> write test to /dev/hdh1) so badly that the partion information changed
> from type 83 to type 3 (Xenix), and the contents of a reiser partition so
> badly damaged that a --rebuild-tree and later a --rebuild-sb to reiserfsck
> didn't restore it to usable. (I put those options in at the request of
> reiserfsck, and I haven't wiped the drive yet if someone would like
> further tests against the reiserfs partition).
We are interested in such a damaged partitions that makes current reiserfsck
to segfault or to incorrectly repair FS (incorrectly in the meaning that
subsequent reiserfsck run finds more errors)
Is this the case with you?
Bye,
Oleg
next prev parent reply other threads:[~2002-04-11 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 17:39 New IDE code and DMA failures Denis Vlasenko
2002-04-11 12:05 ` Martin Dalecki
2002-04-11 18:44 ` Denis Vlasenko
2002-04-11 12:52 ` Martin Dalecki
2002-04-11 19:17 ` Denis Vlasenko
2002-04-11 15:48 ` Vojtech Pavlik
2002-04-12 14:47 ` Denis Vlasenko
2002-04-11 13:05 ` Ted Deppner
2002-04-11 14:10 ` Oleg Drokin [this message]
2002-04-13 0:58 ` Ted Deppner
2002-04-13 7:07 ` Oleg Drokin
-- strict thread matches above, loose matches on Subject: below --
2002-04-11 16:27 Petr Vandrovec
2002-04-13 1:02 ` Ted Deppner
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=20020411181027.A1870@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=ted@psyber.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