From: Folkert van Heusden <folkert@vanheusden.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.27] filesystem (ext3) corruption (access beyond end)
Date: Thu, 4 Dec 2008 18:01:53 +0100 [thread overview]
Message-ID: <20081204170153.GJ1547@vanheusden.com> (raw)
Hi,
With 2.6.26 and 2.6.27 a system of mine (a P4 with HT and IDE disk) gets
massive disk-corruption: in dmesg warnings for access beyond drive end.
Now this bug did not happen in 2.6.18 (debian kernel) and it seems to
be gone in 2.6.28-rc* as well.
My question now is: should it still be investigated?
Folkert van Heusden
--
To MultiTail einai ena polymorfiko ergaleio gia ta logfiles kai tin
eksodo twn entolwn. Prosferei: filtrarisma, xrwmatismo, sygxwneysi,
diaforetikes provoles. http://www.vanheusden.com/multitail/
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com
next reply other threads:[~2008-12-04 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 17:01 Folkert van Heusden [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-05 9:46 [2.6.27] filesystem (ext3) corruption (access beyond end) Randolf Pohl
2008-12-06 15:53 ` Folkert van Heusden
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=20081204170153.GJ1547@vanheusden.com \
--to=folkert@vanheusden.com \
--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