All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Sommer" <joerg@alea.gnuu.de>
To: Theodore Tso <tytso@mit.edu>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	389772@bugs.debian.org, paulus@au.ibm.com,
	linux-ext4@vger.kernel.org
Subject: Re: Bug#389772: e2fsprogs: e2fsck produces broken htree on ppc
Date: Sun, 1 Oct 2006 01:57:17 +0200	[thread overview]
Message-ID: <20060930235717.GA3403@alea.gnuu.de> (raw)
In-Reply-To: <20060929211556.GA11017@thunk.org>

[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]

Hello Theodore,

Theodore Tso schrieb am Fri 29. Sep, 17:15 (-0400):
> If the filesystem is empty (or at least no no hashtree directories),
> then when the kernel creates new directories and expands to the point
> where they become indexed, they will be indexed with the PPC variant
> of the hash algorithm.  This will be self consistent, and everything
> will work fine --- until the filesystem gets corrupted to the point
> where e2fsprogs needs to rebuild one or more hashed directories.  At
> that point the directories will be rebuilt using the same conventions
> used by all other conventions, but the directories will no longer be
> useful on the PPC kernel.
> 
> Joerg, can you confirm this?

Yes.

> On a PPC machine, can you create a smallish ext3 filesystem (say, 4-8
> megabytes), create a directory with enough files in it that it becomes
> indexed (verify using lsattr), and show that it works just fine on a
> PPC.  Now take that image, and transfer it to an x86 machine;

I don't have a x86 machine.

> you should find that the kernel can't look up any of the directories on
> the x86 machine.  If you then run e2fsck -fD on that filesystem
> (running the e2fsck on either x86 or PPC; it shouldn't make a
> difference), then the resulting filesystem should work just fine on the
> x86, and fail on the PPC.

I put two files at http://www.minet.uni-jena.de/~joergs/ img-broken and
img-working. In the last image, img-working, I can access all files,
especially "test/broken fürß". The first image, img-broken, is the
image after running e2fsck -Df on img-working. So you can test if one
of these images work on x86, especially if the file "test/broken fürß"
is accessable.

Bye, Jörg.
-- 
Wer A sagt, muß nicht B sagen. Er kann auch erkennen, daß A falsch war.
      	    	      	       	       	    	(Erich Kästner)

[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]

      reply	other threads:[~2006-10-01  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060927122251.GA732@alea.gnuu.de>
2006-09-29  1:08 ` Bug#389772: e2fsprogs: e2fsck produces broken htree on ppc Theodore Tso
2006-09-29 17:15   ` Andreas Dilger
2006-09-29 21:15     ` Theodore Tso
2006-09-30 23:57       ` Jörg Sommer [this message]

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=20060930235717.GA3403@alea.gnuu.de \
    --to=joerg@alea.gnuu.de \
    --cc=389772@bugs.debian.org \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=paulus@au.ibm.com \
    --cc=tytso@mit.edu \
    /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.