From: Charles-Edouard Ruault <ce@ruault.com>
To: stephane@tuxfinder.org
Cc: Jeff Merkey <jmerkey@timpanogas.org>, J Sloan <jjs@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: File system Corruption with 2.4.16
Date: Sat, 01 Dec 2001 20:54:18 -0800 [thread overview]
Message-ID: <3C09B3FA.61777E84@ruault.com> (raw)
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>
The symlink problem you're reporting is exactly what i've been experiencing among
other things ...
on both systems i had multiple ext2 partitions and one reseirfs partition.
The problem showed up after a few days of uptime. Both machines where not heaviliy
loaded and had no memory shortage.
It looks like it also happened on my third system, which had only 2 ext2 partitions
. I was able to clean up this one with fsck and rebooted safely to 2.4.14 ....
Given the fact that i'm not the only one to see the problem with 2.4.16 i'll safely
backtrack all my machines to 2.4.14 ...
If i can be of any help to pinpoint the problem please let me know. But since i'm
not a kernel hacker i don't think i'll be pluging into the sources myself on my own
!
Thanks for the feedback !
Charles-Edouard Ruault
Stephane Jourdois wrote:
> 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)
>
> 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 ///
next prev parent reply other threads:[~2001-12-02 4:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 22:08 File system Corruption with 2.4.16 Charles-Edouard Ruault
2001-12-01 22:22 ` J Sloan
2001-12-01 22:34 ` Charles-Edouard Ruault
2001-12-01 23:47 ` Jeff Merkey
2001-12-01 23:54 ` J Sloan
2001-12-02 0:52 ` Jeff Merkey
2001-12-02 1:31 ` Stephane Jourdois
2001-12-02 2:58 ` Jeff Merkey
2001-12-02 4:54 ` Charles-Edouard Ruault [this message]
2001-12-02 6:00 ` Tom Vier
2001-12-02 6:27 ` Charles-Edouard Ruault
2001-12-02 6:03 ` J Sloan
[not found] ` <1007273541.408.5.camel@psuedomode>
2001-12-02 6:51 ` Charles-Edouard Ruault
2001-12-02 7:25 ` J Sloan
2001-12-02 12:03 ` Heinz Diehl
2001-12-02 18:11 ` Kenneth Johansson
2001-12-02 18:55 ` Rene Rebe
2001-12-02 6:08 ` J Sloan
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=3C09B3FA.61777E84@ruault.com \
--to=ce@ruault.com \
--cc=jjs@pobox.com \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephane@tuxfinder.org \
/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