All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pascal Terjan <pterjan@mandriva.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Andrey Borzenkov <arvidjaar@mail.ru>,
	pterjan@mandriva.org, linux-ext4@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Possible ext3 corruption with 1K block size
Date: Thu, 16 Oct 2008 15:47:40 +0200	[thread overview]
Message-ID: <1224164860.11578.14.camel@plop> (raw)
In-Reply-To: <48F601A5.1050405@redhat.com>

Le mercredi 15 octobre 2008 à 09:43 -0500, Eric Sandeen a écrit :
> Andrey Borzenkov wrote:
> > On Wednesday 15 October 2008, Eric Sandeen wrote:
> 
> 
> >> 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?"  :)
> >>
> > 
> > May be RH will do? :)
> 
> I did try a 1k-block root fs Fedora install, and didn't see any problems...
> 
> > As indicated by last comment, Pascal has some ways to trigger it; I
> > forgot to Cc to him initially; doing it now.
> 
> Ok, good deal.
> 

On my test machine I reproduce it easily : rpm --rebuilddb and if the db
is not detected to be corrupted yet it will be after installing a few
packages (tested again with 2.6.27).

If I do the rebuilddb on a 2.6.17 and then reboot on a recent kernel,
then I can install/uninstall thousands of packages without any
corruption.

I wanted to try a few things including copying the partition to a file
and trying to reproduce in a vm.

Given how I can reproduce and repair it i can even write a bisecting
script which would basically be an initscript which would do

if on test kernel
- rebuild the db
- install 10 rpm
- remove the 10 rpm
- check the db
- do the good/bad
- reboot onto 2.6.17
else if on 2.6.17
- rebuild the db
- build the kernel
- reboot on test kernel

and let it run :)

All I need is to find some time with nothing more urgent...

  reply	other threads:[~2008-10-16 13:47 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
2008-10-15 14:24   ` Andrey Borzenkov
2008-10-15 14:43     ` Eric Sandeen
2008-10-16 13:47       ` Pascal Terjan [this message]
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=1224164860.11578.14.camel@plop \
    --to=pterjan@mandriva.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pterjan@mandriva.org \
    --cc=sandeen@redhat.com \
    /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.