Hi Dieter Wirz, Thank you for reply,
I think there are enough inodes available for a partition you see output of tune2fs command.(my busybox df doesn't support df -i command). # tune2fs -l /dev/mmcblk0p16 | grep -i inode Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse Inode count: 128016 Free inodes: 107941 Inodes per group: 2032 Inode blocks per group: 254 First inode: 11 Inode size: 128 Journal inode: 8 Journal backup: inode blocks First error inode #: 0 Last error inode #: 0 I tested with tar file as well. Result is same as tar.gz file. Thank you, Regards, Ankur On Friday, 16 June 2017 20:49:47 UTC+5:30, Dieter Wirz wrote: > > Hello > > On Thu, May 25, 2017 at 8:25 PM, Ankur Tank <art...@gmail.com > <javascript:>> wrote: > > Hello Experts, > > > > We are seeing fragmentation and resultant eMMC partition corruption when > > extracting tar file with 81000 files of 4k size. > > > > Detailed steps are listed in Test_steps.txt file and other attached tars > > contain required scripts to big tar file and other test scripts. > > > > In test is very simple, > > 1. we have tar with 81000 number of 4k size file > > 2. we ran latest debian from Beagleboard.org from Micro SD Card > > 3. Partitioned eMMC in two partitions > > 4. Then mounted one of the partition and started extracting big tar file > on > > that partition. > > > > This results in below Error. > > EXT4-fs error (device mmcblk1p2) in ext4_do_update_inode:4665: Journal > has > > aborted > > [12064.194479] EXT4-fs error (device mmcblk1p2) in > add_dirent_to_buf:1921: > > Journal has aborted > > [12064.209980] EXT4-fs error (device mmcblk1p2) in > > ext4_do_update_inode:4665: Journal has aborted > > [12064.223765] EXT4-fs error (device mmcblk1p2) in ext4_create:2455: IO > > failure > > [12064.238221] EXT4-fs error (device mmcblk1p2): > > ext4_journal_check_start:56: Detected aborted journal > > [12064.247591] EXT4-fs (mmcblk1p2): Remounting filesystem read-only > > Did u check the the number of inodes on your device mmcblk1p2 (df -i). > The number _must_ be over 81000. You can tune the number of inodes > while formatting (man mkfs.ext4) with -N. You should play around with > -b and other parameters as well... > > tar.gz is nothing else than a gzipped tar file. Did you try the same > experiment with a uncompressed tar having the same size ? > > > > Strange enough this test works fine on Angstrom OS image > > Maybe Angstrom mkfs produces a different filesystem with different # of > inodes > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/df1b81a6-bd78-4edc-96b3-7856ff28852c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
