From: J Sloan <jjs@pobox.com>
To: Charles-Edouard Ruault <ce@ruault.com>
Cc: stephane@tuxfinder.org, Jeff Merkey <jmerkey@timpanogas.org>,
linux-kernel@vger.kernel.org
Subject: Re: File system Corruption with 2.4.16
Date: Sat, 01 Dec 2001 22:03:00 -0800 [thread overview]
Message-ID: <3C09C414.5D9C9CAE@pobox.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> <3C09B3FA.61777E84@ruault.com>
Charles-Edouard Ruault wrote:
> 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
Interesting - maybe I'm just lucky, but my
systems have never been more stable than
they are now under 2.4.16 -
The plot thickens!
jjs
next prev parent reply other threads:[~2001-12-02 6:03 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
2001-12-02 6:00 ` Tom Vier
2001-12-02 6:27 ` Charles-Edouard Ruault
2001-12-02 6:03 ` J Sloan [this message]
[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=3C09C414.5D9C9CAE@pobox.com \
--to=jjs@pobox.com \
--cc=ce@ruault.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 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.