From: "Steve Best" <sbest@us.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
jfs-discussion@dwoss.lotus.com,
Jeff Garzik <jgarzik@mandrakesoft.com>,
lkml <linux-kernel@vger.kernel.org>,
David Mansfield <lkml@dm.ultramaster.com>
Subject: Re: [Jfs-discussion] Re: severe FS corruption with 2.4.6-pre2 + IBM jfs 0.3.4 patch
Date: Fri, 15 Jun 2001 08:11:54 -0500 [thread overview]
Message-ID: <OF336B3F96.2AD61AA8-ON85256A6C.0047D9E1@raleigh.ibm.com> (raw)
On Fri, Jun 15, 2001 at 01:55:05AM Andi Kleen wrote:
> On Thu, Jun 14, 2001 at 02:25:06PM -0400, Jeff Garzik wrote:
>> 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..
> rm -rf not working correctly is a kind of show stopper bug ATM though.
> Hopefully it can be fixed soon.
Andi,
The rm -rf problem is our topic priority and should be fixed in less
that a week.
Steve
next reply other threads:[~2001-06-15 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-15 13:11 Steve Best [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-14 18:18 severe FS corruption with 2.4.6-pre2 + IBM jfs 0.3.4 patch Alan Cox
2001-06-14 18:25 ` Jeff Garzik
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=OF336B3F96.2AD61AA8-ON85256A6C.0047D9E1@raleigh.ibm.com \
--to=sbest@us.ibm.com \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jfs-discussion@dwoss.lotus.com \
--cc=jgarzik@mandrakesoft.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).