All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Pascal Terjan <pterjan@mandriva.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 09:38:33 -0500	[thread overview]
Message-ID: <48F751E9.8070705@redhat.com> (raw)
In-Reply-To: <1224164860.11578.14.camel@plop>

Pascal Terjan wrote:
> 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.

so it seems to be the database rebuilding, under a recent kernel, which
causes the problem?  installing under a recent kernel is ok, as long as
the db was created on an older kernel?

Ok that's a good clue...

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Eric Sandeen <sandeen@redhat.com>
To: Pascal Terjan <pterjan@mandriva.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 09:38:33 -0500	[thread overview]
Message-ID: <48F751E9.8070705@redhat.com> (raw)
In-Reply-To: <1224164860.11578.14.camel@plop>

Pascal Terjan wrote:
> 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.

so it seems to be the database rebuilding, under a recent kernel, which
causes the problem?  installing under a recent kernel is ok, as long as
the db was created on an older kernel?

Ok that's a good clue...

-Eric

  reply	other threads:[~2008-10-16 14:38 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
2008-10-16 14:38         ` Eric Sandeen [this message]
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=48F751E9.8070705@redhat.com \
    --to=sandeen@redhat.com \
    --cc=arvidjaar@mail.ru \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pterjan@mandriva.com \
    --cc=pterjan@mandriva.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.