From: Chris Mason <mason@suse.com>
To: Dirk Mueller <dmuell@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.4.19-pre7 / corruption on unwanted reboot
Date: 06 May 2002 10:26:00 -0400 [thread overview]
Message-ID: <1020695160.3946.2155.camel@tiny> (raw)
In-Reply-To: <20020506135941.GA16598@matrix.wg>
On Mon, 2002-05-06 at 09:59, Dirk Mueller wrote:
> On Mon, 06 Mai 2002, Chris Mason wrote:
>
> > Please tell us everything about your IDE config. Jens and I are already
> > trying to track down some odd reiserfs + ide problems on 2.4.19pre7, but
> > so far that was only with our barrier write patches applied.
>
> There is not much common. two of them are VIA 686 southbridge (KT133A,
> KT333), one is something older, a Pentium chipset.
>
> DMA 100 and DMA 66. We all use those Maxtor 80GB EIDE disks.
Any suggestions on how I might reproduce locally?
-chris
next prev parent reply other threads:[~2002-05-06 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 21:11 2.4.19-pre7 / corruption on unwanted reboot Dirk Mueller
2002-05-05 2:07 ` Chris Mason
2002-05-06 12:36 ` Dirk Mueller
2002-05-06 12:54 ` Chris Mason
2002-05-06 13:59 ` Dirk Mueller
2002-05-06 14:26 ` Chris Mason [this message]
2002-05-06 18:37 ` Dirk Mueller
2002-05-05 8:09 ` Oleg Drokin
2002-05-06 10:59 ` Hans Reiser
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=1020695160.3946.2155.camel@tiny \
--to=mason@suse.com \
--cc=dmuell@gmx.net \
--cc=reiserfs-list@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 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.