From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-ext4@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Possible ext3 corruption with 1K block size
Date: Wed, 15 Oct 2008 07:24:38 +0400 [thread overview]
Message-ID: <200810150724.42180.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1272 bytes --]
There is long standing open bug report on Mandriva which is currently
beieved to have root cause in file system corruption. It shows itself
in RPM DB corruption (at least, there is no other known method to trigger
it). So far all reported cases happened on filesystem with 1K block size
and stopped when RPM DB was moved to FS with 4K block size.
There are also similar RH reports as well.
Here are references:
https://qa.mandriva.com/show_bug.cgi?id=32547
This one is rather long. Interesting bits are probably around
https://qa.mandriva.com/show_bug.cgi?id=32547#c177
https://qa.mandriva.com/show_bug.cgi?id=32547#c148 (many users reporting
dumpe2fs)
https://bugzilla.redhat.com/show_bug.cgi?id=230362
https://bugzilla.redhat.com/show_bug.cgi?id=375931
https://bugzilla.redhat.com/show_bug.cgi?id=305301
The Mandriva bugzilla also mentions this mail from Stephen Tweedie
http://lkml.org/lkml/2007/9/18/232
which indicates some issues with 1K blocks, but according to last comment:
https://qa.mandriva.com/show_bug.cgi?id=32547#c300
it is still present in 2.6.27 (at least was present on -rc6)
There was a kernel bug report http://bugzilla.kernel.org/show_bug.cgi?id=11564,
but in this case it was identified as hardware issue.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-10-15 3:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 3:24 Andrey Borzenkov [this message]
2008-10-15 12:49 ` Possible ext3 corruption with 1K block size Eric Sandeen
2008-10-15 14:24 ` Andrey Borzenkov
2008-10-15 14:43 ` Eric Sandeen
2008-10-16 13:47 ` Pascal Terjan
2008-10-16 14:38 ` Eric Sandeen
2008-10-16 14:40 ` Pascal Terjan
2008-12-18 18:12 ` Jan Kara
2008-12-18 18:20 ` Eric Sandeen
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=200810150724.42180.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-ext4@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).