Comment 11 for bug 7454

Message-ID: <email address hidden>
Date: Wed, 18 Aug 2004 03:40:18 +1000 (EST)
From: Finn Thain <email address hidden>
To: Bastian Blank <email address hidden>, David Kimdon <email address hidden>
cc: <email address hidden>
Subject: Re: genext2fs - generates completely broken images on s390

On Tue, 17 Aug 2004, Bastian Blank wrote:

> On Tue, Aug 17, 2004 at 11:38:38PM +1000, Finn Thain wrote:
> > I don't have an s390 to test on unfortunately, so would you please try
> > a couple of tests to help me isolate this problem.
>
> You have, ask http://db.debian.org/ for the developer machines.

Cool. David, what's the procedure for obtaining access to raptor?

> > - does compiling genext2fs generate any warnings?
>
> Ask http://buildd.debian.org/.

Very nice. I had no idea that site existed. Interesting to note that make
check fails, but that is not suprising -- it fails where fsck succeeds on
my machines. I'd better look at that too.

> > - does the following generate fsck errors (apart from the lost+found not
> > present warning, and the missing volume UUID)?
> >
> > $ genext2fs -b 5876 -r 0 /tmp/whatever
> > $ fsck.ext2 /tmp/whatever
>
> | $ genext2fs -b 5876 -r 0 /tmp/whatever
> | $ fsck.ext2 /tmp/whatever
> | e2fsck 1.35 (28-Feb-2004)
> | Note: if there is several inode or block bitmap blocks
> | which require relocation, or one part of the inode table
> | which must be moved, you may wish to try running e2fsck
> | with the '-b 5881' option first. The problem may lie only
> | with the primary block group descriptor, and the backup
> | block group descriptor may be OK.
> |
> | Block bitmap for group 0 is not in group. (block 50331648)
> | Relocate<y>? cancelled!
> |
> | Inode bitmap for group 0 is not in group. (block 67108864)
> | Relocate<y>? cancelled!
> |
> | Inode table for group 0 is not in group. (block 83886080)
> | WARNING: SEVERE DATA LOSS POSSIBLE.
> | Relocate<y>? cancelled!
> |
> | Filesystem did not have a UUID; generating one.
>
> > I tried this on my celeron, it works ok for me.
>
> You tried it on a 32bit little-endian machine. I try it on a
> 64bit/31bit big-endian machine.

I also tested on my alpha (64-bit little endian) and it works ...
interesting.

Looks like I'm gonna need that s390 account. Thanks for your help.

-F

> Bastian
>
>