| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Nov 2014 14:09:32 +0100 From: Angelo Dureghello <angelo70@...il.com> To: linux-ext4@...r.kernel.org Subject: Re: ext4 errors on kernel 3.17.0 Hi, still fighting on this. I am trying now with a simple mkfs.ext3 on the mmc card, verifying just after with fsck.ext3. On kernel 3.5.1 the fsck get a "clean" state, on 3.17.0 i am full of errors. [root@...ix ~]# fsck.ext3 /dev/mmcblk0p1 e2fsck 1.42.4 (12-June-2012) ext2fs_check_desc: Corrupt group descriptor: bad block for block bitmap fsck.ext3: Group descriptors look bad... trying backup blocks... Superblock has an invalid journal (inode 8). Clear<y>? Automount: /dev/mmcblk0p1 inserted Automount: DEVICE LOCK found quiting... yes *** ext3 journal has been deleted - filesystem is now ext2 only *** /dev/mmcblk0p1 was not cleanly unmounted, check forced. Resize inode not valid. Recreate<y>? yes Pass 1: Checking inodes, blocks, and sizes The bad block inode looks invalid. Clear<y>? yes Root inode is not a directory. Clear<y>? yes Inode 5 has EXTENTS_FL flag set on filesystem without extents support. Clear<y>? yes Inode 6 has EXTENTS_FL flag set on filesystem without extents support. Clear<y>? yes Inode 8 has EXTENTS_FL flag set on filesystem without extents support. Clear<y>? yes Inode 9 has EXTENTS_FL flag set on filesystem without extents support. Clear<y>? yes Inode 10 has EXTENTS_FL flag set on filesystem without extents support. Clear<y>? .... (continue) The card is detected correctly, exactly at the same way on both kernels mmc0: host does not support reading read-only switch. assuming write-enable. mmc0: new high speed SDHC card at address 0002 mmcblk0: mmc0:0002 SD 7.46 GiB mmcblk0: p1 But, mkfs.ext3 gives different output: |kernel 3.5.1 | || |[root@...ix ~]# mkfs.ext3 /dev/mmcblk0p1 | |mke2fs 1.42.4 (12-June-2012) | |Filesystem label= | |OS type: Linux | |Block size=4096 (||log||=2) | |Fragment size=4096 (||log||=2) | |Stride=0 blocks, Stripe width=0 blocks | |488640 inodes, 1952881 blocks | |97644 blocks (5.00%) reserved ||for||the super user | |First data block=0 | |Maximum filesystem blocks=2000683008 | |60 block groups | |32768 blocks per group, 32768 fragments per group | |8144 inodes per group | |Superblock backups stored on blocks: | |||32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 | || |Allocating group tables: done | |Writing inode tables: done | |Creating journal (32768 blocks): done | |Writing superblocks and filesystem accounting information: done | || |kernel 3.17.0 | || |[root@...ix ~]# mkfs.ext3 /dev/mmcblk0p1 | |mke2fs 1.42.4 (12-June-2012) | |Filesystem label= | |OS type: Linux | |Block size=4096 (||log||=2) | |Fragment size=4096 (||log||=2) | |Stride=0 blocks, Stripe width=0 blocks | |240000 inodes, 959232 blocks | |47961 blocks (5.00%) reserved ||for||the super user | |First data block=0 | |Maximum filesystem blocks=985661440 | |30 block groups | |32768 blocks per group, 32768 fragments per group | |8000 inodes per group | |Superblock backups stored on blocks: | |||32768, 98304, 163840, 229376, 294912, 819200, 884736 | || |Allocating group tables: done | |Writing inode tables: done | |Creating journal (16384 blocks): done | |Writing superblocks and filesystem accounting information: done The recent 3.17.0 kernel shows - about half of |||"Maximum filesystem blocks" - |||8000 inodes per group instead of 8144 on 3.5.1 - about half of the inodes. Could this be the reason of the mmc issues i am having ? many thanks | -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists