From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Mansfield <lkml@dm.ultramaster.com>,
lkml <linux-kernel@vger.kernel.org>,
jfs-discussion@oss.lotus.com
Subject: Re: severe FS corruption with 2.4.6-pre2 + IBM jfs 0.3.4 patch
Date: Thu, 14 Jun 2001 14:25:06 -0400 [thread overview]
Message-ID: <3B290182.42DE3E1@mandrakesoft.com> (raw)
In-Reply-To: <E15Abh0-000564-00@the-village.bc.nu>
Alan Cox wrote:
>
> > It's probably a JFS issue, but I thought I'd report this in case someone
> > is collecting and correlating filesystem corruption messages (Alan?).
> > Here is my sad story.
>
> I get as far as 'using jfs' and delete them
Understandable but FWIW they have apparently passed a night of
stress-kernel (cerberus) testing on the latest jfs..
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-14 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-12 20:39 severe FS corruption with 2.4.6-pre2 + IBM jfs 0.3.4 patch David Mansfield
2001-06-14 18:18 ` Alan Cox
2001-06-14 18:25 ` Jeff Garzik [this message]
2001-06-15 6:55 ` [Jfs-discussion] " Andi Kleen
2001-06-15 9:08 ` Luigi Genoni
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=3B290182.42DE3E1@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jfs-discussion@oss.lotus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@dm.ultramaster.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;
as well as URLs for NNTP newsgroup(s).