On Thu, Mar 20, 2008 at 01:08:01AM +0530, Aneesh Kumar K.V wrote: > Hi Ted, > > While testing on powerpc i found that e2fsck is getting confused about > fast symlink on powerpc. On x86_64 it works fine. > > lrwxrwxrwx 1 root root 60 Mar 19 15:18 d -> /usr/share/icons/hicolor/48x48/apps/gnome-netstatus-txrx.png > [root@gekko-lp2 ~]# /usr/local/e2fsprogs/sbin/debugfs /dev/sda7 > debugfs 1.40.8 (13-Mar-2008) > debugfs: stat d > Inode: 24483 Type: symlink Mode: 0777 Flags: 0x80000 > Generation: 2913520215 > User: 0 Group: 0 Size: 60 > File ACL: 0 Directory ACL: 0 > Links: 1 Blockcount: 8 > Fragment: Address: 0 Number: 0 Size: 0 > ctime: 0x47e166f9 -- Wed Mar 19 15:18:17 2008 > atime: 0x47e166fb -- Wed Mar 19 15:18:19 2008 > mtime: 0x47e166f9 -- Wed Mar 19 15:18:17 2008 > Size of extra inode fields: 28 > BLOCKS: > > debugfs: > > root@gekko-lp2 ~]# /usr/local/e2fsprogs/sbin/e2fsck -f /dev/sda7 > e2fsck 1.40.8 (13-Mar-2008) > Pass 1: Checking inodes, blocks, and sizes > Error while reading over extent tree in inode 24483: Corrupt extent > header > Clear inode<y>? yes > > Inode 24483, i_blocks is 8, should be 0. Fix<y>? yes > > Fast symlink 100055 has EXTENT_FL set. Clear<y>? > The extent support on powerpc doesn't seems to work with e2fsprogs. make check on e2fsprogs on powerpc gives f_extents: basic extents support: failed -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
