Dave Chinner wrote:
> Adding xfs@xxxxxxxxxxx to the cc list so all the XFS folk see this.
> On Wed, Oct 01, 2008 at 10:38:22PM +0200, Tobias Frost wrote:
>> (Note: Please CC me, as I am NOT on the lkml!!)
>> Some time ago, I discovered some problems with xfs. Unfortunatly, I had
>> no time diving into it. However, some weeks ago some other people
>> running debian on ARM machines confirmed the problem on their machines
>> starting at , so I think it is appropitate to at least report it.
>> It has also been seen on 2.6.27-rc4 .
>> summary: the xfs partition corrupts almost immediatly after creation. I
>> had the impression, that the first unlink (rm) causes the corruption,
>> but this might be just an impression.
>> During the tests I made, I conserved a image of the corrupted filesystem
>> which I can make available on request (it's 26 Mbyte, gzipped).
>> Please let me know how I can assist you in finding the problem.
>>  http://lists.debian.org/debian-arm/2008/08/msg00155.html
>>  http://lists.debian.org/debian-arm/2008/08/msg00184.html
>> Best regards,
>> Tobias Frost
You could try undoing this:
/* ARM old ABI has some weird alignment/padding */
#if defined(__arm__) && !defined(__ARM_EABI__)
#define __arch_pack __attribute__((packed))
and just define __arch_pack to nothing unconditionally, to see if that's
Or if someone can provide an xfs.ko, or point "pahole" at it yourself,
and see if xfs_dir2_sf_hdr, xfs_dir2_sf_entry, and xfs_dir2_sf look more
otherwise I will give this a whirl in the emulator again...