From: J Sloan <jjs@pobox.com>
To: Jeff Merkey <jmerkey@timpanogas.org>
Cc: Charles-Edouard Ruault <ce@ruault.com>, linux-kernel@vger.kernel.org
Subject: Re: File system Corruption with 2.4.16
Date: Sat, 01 Dec 2001 15:54:27 -0800 [thread overview]
Message-ID: <3C096DB3.204CE41C@pobox.com> (raw)
In-Reply-To: <3C0954D5.6AA3532B@ruault.com> <3C09580F.5F323195@pobox.com> <3C095B0B.7EA478C1@ruault.com> <003601c17ac2$7a8dec10$f5976dcf@nwfs>
Jeff Merkey wrote:
> I am seeing corruption on 2.4.16 (2.4.17-pre1/2) as well. Whatever this
> gentlemen is doing is making it show up quicker, but I am on my fourth
> interation of fsck'ing 2.4.16 on my production server with NWFS builds. I
> am looking through Al Viros's inode code changes to see if there's hole
> somewhere. This problem appears to be related to low memory conditions. I
> see it when memory is getting low. May be VM related as well.
Just to be positive, can you reproduce the
problem without nwfs?
cu
jjs
next prev parent reply other threads:[~2001-12-01 23:55 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 [this message]
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
[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=3C096DB3.204CE41C@pobox.com \
--to=jjs@pobox.com \
--cc=ce@ruault.com \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.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.