On 1/27/13 4:52 PM, Lluís Batlle i Rossell wrote: > Hello, > > I'm using linux 3.7.3 in both machines (x86_64 and armv5tel), and I created > a volume in x86_64 to be the rootfs for the ARM. All fine, until I plugged it > into the ARM (Log below). > > Given the corruption, I used xfs_repair in the x86_64, moved a lot of files into lost+found, plugged it back to the ARM, booted, and corruption again. > > In the same USB HD, in the same ARM, and this same way, I've used succesfully > ext4 and btrfs for a long time. Is there any known issue with ARM? > > Thank you, > Lluís. > > ---------------------- > starting systemd... > systemd 197 running in system mode. (+PAM -LIBWRAP -AUDIT -SELINUX +IMA +SYSVINIT -LIBCRYPTSETUP +GCRYPT +ACL +XZ) > > Welcome to NixOS 0.2pre-4eb2b09-af495e0! > > Failed to insert module 'autofs4' > dea96000: 58 46 53 42 00 00 10 00 00 00 00 00 01 bd 26 f0 XFSB..........&. > XFS (sda1): Internal error xfs_da_do_buf(2) at line 2192 of file fs/xfs/xfs_da_btree.c. Caller 0xbf057e68 So this was trying to read a dir2 directory metadata leaf block, and it didn't find the right magic. XFSB is superblock magic . . . I tested an image which (I think) contains every dir2 format, created on x86_64 (under a RHEL6 3.2 kernel) and checked it on ARM (a raspberry pi 3.2.24 kernel) so it's not really quite an apples to apples test. Does the filesystem check clean on x86_64 right after you create it? How did you create it? -Eric _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
