public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ted Deppner <ted@psyber.com>
To: Oleg Drokin <green@namesys.com>
Cc: ted@psyber.com, linux-kernel@vger.kernel.org,
	Hans Reiser <reiser@namesys.com>
Subject: Re: New IDE code and DMA failures
Date: Fri, 12 Apr 2002 17:58:05 -0700	[thread overview]
Message-ID: <20020413005805.GA17025@dondra.ofc.psyber.com> (raw)
In-Reply-To: <200204111236.g3BCaMX10247@Port.imtp.ilyichevsk.odessa.ua> <20020411130544.GA8163@dondra.ofc.psyber.com> <20020411181027.A1870@namesys.com>

On Thu, Apr 11, 2002 at 06:10:27PM +0400, Oleg Drokin wrote:
> 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?

Subsequent runs of reiserfsck are no longer finding new errors.  There
were several cases where --rebuild-tree segfaulted reiserfsck -- HOWEVER
this was before I got the DMA errors ironed out.

Now that the DMA errors are taken care of, I've not been able to get
reiserfsck to behave oddly.

-- 
Ted Deppner
http://www.psyber.com/~ted/

  reply	other threads:[~2002-04-13  0:58 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
2002-04-13  0:58     ` Ted Deppner [this message]
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=20020413005805.GA17025@dondra.ofc.psyber.com \
    --to=ted@psyber.com \
    --cc=green@namesys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reiser@namesys.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