From: jmerkey <jmerkey@utah-nac.org>
To: jmerkey <jmerkey@utah-nac.org>
Cc: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>,
Parag Warudkar <kernel-stuff@comcast.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ext3 bug
Date: Mon, 28 Feb 2005 21:06:11 -0700 [thread overview]
Message-ID: <4223EA33.20406@utah-nac.org> (raw)
In-Reply-To: <4223E9C8.5040604@utah-nac.org>
jmerkey wrote:
> Jean-Marc Valin wrote:
>
>> Le lundi 28 février 2005 à 08:31 -0700, jmerkey a écrit :
>>
>>
>>> I see this problem infrequently on systems that have low memory
>>> conditions and
>>> with heavy swapping. I have not seen it on 2.6.9 but I have seen
>>> it on 2.6.10.
>>
>>
>> My machine has 1 GB RAM and I wasn't using much of it at that time (2GB
>> free on the swap), so I doubt that's the problem in my case.
>>
>> Jean-Marc
>>
>>
>>
> Running the ext2 recover program seems to trigger some good bugs in
> 2.6.10 with ext3 -- try it. I was doing this
> to test some disk tools and I managed to cause these errors with
> forcing ext2 recovery from an ext3 fs (which is
> probably something to be expected. The recover tools need to get
> syncrhonized -- have not tried with
> mc yet.) Doesn't happen every time though.
>
> Jeff
>
>
>
lde also causes some problems as well with ext3. Just caused one on
2.6.10. stale or poisoned
cache blocks perhaps?
Jeff
next prev parent reply other threads:[~2005-03-01 4:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 7:04 ext3 bug Jean-Marc Valin
2005-02-27 19:06 ` Parag Warudkar
2005-02-27 19:27 ` Dave Jones
2005-02-27 19:40 ` Parag Warudkar
2005-02-27 22:58 ` Jean-Marc Valin
2005-02-28 1:10 ` Parag Warudkar
2005-02-28 2:04 ` Jean-Marc Valin
2005-02-28 2:24 ` Parag Warudkar
2005-02-28 15:31 ` jmerkey
2005-02-28 21:50 ` Jean-Marc Valin
2005-03-01 4:04 ` jmerkey
2005-03-01 4:06 ` jmerkey [this message]
2005-03-01 5:25 ` Jeffrey E. Hundstad
2005-03-01 6:38 ` jmerkey
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=4223EA33.20406@utah-nac.org \
--to=jmerkey@utah-nac.org \
--cc=Jean-Marc.Valin@USherbrooke.ca \
--cc=kernel-stuff@comcast.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox