Comment 7 for bug 7454

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

Hi Bastian,

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.

- does compiling genext2fs generate any warnings?

- 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

I tried this on my celeron, it works ok for me. If it works for you, I may
need the contents of the directory you were storing on the image using "-d
./tmp/generic/tree", if possible. If it works for you, there is a good
chance that the absurd positions of the bitmaps and inode tables in your
bug report are caused by the group descriptor getting hosed.

Regards,

Finn Thain