All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-ext4@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Possible ext3 corruption with 1K block size
Date: Wed, 15 Oct 2008 07:49:24 -0500	[thread overview]
Message-ID: <48F5E6D4.8080603@redhat.com> (raw)
In-Reply-To: <200810150724.42180.arvidjaar@mail.ru>

Andrey Borzenkov wrote:
> 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. 

yep, unfortunately IIRC most of the bug is "me too's" and "how do I do
the workaround" :)

> 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

I don't think this is related, in the end... there was some possiblity
of corruption from that, but I think it's doubtful it'd hit 1k block
filesystems more, and in any case, the corruption has been seen since
then if I read it right.

> 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.

My kingdom for a testcase... does anyone have simple steps to reproduce
this?  Or do they all start with "install mandriva on a 1k block size
system?"  :)

-Eric

  reply	other threads:[~2008-10-15 12:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  3:24 Possible ext3 corruption with 1K block size Andrey Borzenkov
2008-10-15 12:49 ` Eric Sandeen [this message]
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:38           ` Eric Sandeen
2008-10-16 14:40           ` Pascal Terjan
2008-12-18 18:12           ` Jan Kara
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=48F5E6D4.8080603@redhat.com \
    --to=sandeen@redhat.com \
    --cc=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 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.