Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S282688AbRLBDAg>; Sat, 1 Dec 2001 22:00:36 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S282692AbRLBDA0>; Sat, 1 Dec 2001 22:00:26 -0500
Received: from vger.timpanogas.org ([207.109.151.240]:15490 "EHLO
	vger.timpanogas.org") by vger.kernel.org with ESMTP
	id <S282688AbRLBDAN>; Sat, 1 Dec 2001 22:00:13 -0500
Message-ID: <006801c17add$42419580$f5976dcf@nwfs>
From: "Jeff Merkey" <jmerkey@timpanogas.org>
To: <stephane@tuxfinder.org>
Cc: "J Sloan" <jjs@pobox.com>, "Charles-Edouard Ruault" <ce@ruault.com>,
        <linux-kernel@vger.kernel.org>
In-Reply-To: <3C0954D5.6AA3532B@ruault.com> <3C09580F.5F323195@pobox.com> <3C095B0B.7EA478C1@ruault.com> <003601c17ac2$7a8dec10$f5976dcf@nwfs> <3C096DB3.204CE41C@pobox.com> <001e01c17acb$a44b69c0$f5976dcf@nwfs> <20011202023145.A1628@emeraude.kwisatz.net>
Subject: Re: File system Corruption with 2.4.16
Date: Sat, 1 Dec 2001 19:58:45 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


----- Original Message -----
From: "Stephane Jourdois" <stephane@tuxfinder.org>
To: "Jeff Merkey" <jmerkey@timpanogas.org>
Cc: "J Sloan" <jjs@pobox.com>; "Charles-Edouard Ruault" <ce@ruault.com>;
<linux-kernel@vger.kernel.org>
Sent: Saturday, December 01, 2001 6:31 PM
Subject: Re: File system Corruption with 2.4.16


> On Sat, Dec 01, 2001 at 05:52:39PM -0700, Jeff Merkey wrote:
> > ----- Original Message ----- From: "J Sloan" <jjs@pobox.com>
> > > Just to be positive, can you reproduce the problem without nwfs?
> > Yes. The problem shows up on ext2 partitions only.
> I destroyed a  hard  disk  yesterday  with  2.4.16,  using  ext3.  A
heavy load
> (compiling The gimp and several other things)  and everything came bad,
symlinks
> didn't work... (for exemple ln -s linux-2.4.17-pre2  linux did a link from
linux
> to linux either using linux-2.4.17-pre2 and /usr/src/linux-2.4.17-pre2.
> > I see this lockup when I have more than  one file system mounted at a
time. It
> > does not happen when only a single  volume (superblock) has been
mounted, only
> > with multiples. Ditto the ext2 corruption. It only shows up when more
than one
> > superblock is active.
> I had only one partition mounted at the moment (/dev/hda1 on / type ext3)

In my setup, the system starts getting low on memory when I mount more than
one.  Could be
related to memory startvation.  I am will look at the lockup on NWFS
tommorow and see if I can make some progress with it.

Jeff


>
> Just in case : debian sid, gcc 2.95.4, everything up to date.
>
>
> We're living in a dangerous world, since 2.4.10...
>
> Ciao,
>
> --
>  ///  Stephane Jourdois        /"\  ASCII RIBBON CAMPAIGN \\\
> (((    Ing?nieur d?veloppement \ /    AGAINST HTML MAIL    )))
>  \\\   6, av. de la Belle Image X                         ///
>   \\\  94440 Marolles en Brie  / \    +33 6 8643 3085    ///

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/