ext4 - 52.2% non-contiguous
I'm trying to understand what is causing fsck to report /dev/sda4 being
highly fragmented. The filesystem is only a couple days old. I created
the it with mke2fs -t ext4.
After initially building the filesystem I ran fsck which showed something
like 0.7% if I remember correctly. I then copied about 60GB from an ext3
via rsync after which the fragmentation showed up.
I'm running Sid, 2.6.30-1-amd64 and have e2fsprogs 1.41.7-1.
Here is the snippet after a forced fsck on reboot.
Mon Jul 6 17:43:17 2009: Activating swap...done.
Mon Jul 6 17:43:17 2009: Checking root file system...fsck 1.41.7 (29-June-2009)
Mon Jul 6 17:43:17 2009: \002/dev/sda3: 141728/917504 files (0.2% non-contiguous), 774394/3664828 blocks
Mon Jul 6 17:43:17 2009: done.
Mon Jul 6 17:43:17 2009: Setting the system clock.
Mon Jul 6 17:43:18 2009: Cleaning up ifupdown....
Mon Jul 6 17:43:18 2009: Loading kernel modules...done.
Mon Jul 6 17:43:18 2009: Checking file systems...fsck 1.41.7 (29-June-2009)
Mon Jul 6 17:43:18 2009: \002/dev/sda1: 28/26104 files (7.1% non-contiguous), 24372/104388 blocks
Mon Jul 6 17:43:19 2009: \002/dev/sda4: 16776/14278656 files (52.2% non-contiguous), 20261557/57111075 blocks
Mon Jul 6 17:43:30 2009: done.
This is a snippet from e2fsck -fpDC0 -E fragcheck /dev/sda4 the full
7000 lines are here http://pastebin.com/f62a00b8c
2490449: expecting 10078208 actual extent phys 10140672 log 1024 len 107
2490449: expecting 10140779 actual extent phys 22521929 log 1131 len 10
2490450: expecting 10076160 actual extent phys 10078208 log 512 len 48
2490451: expecting 10079232 actual extent phys 10138112 log 512 len 454
2490452: expecting 10079744 actual extent phys 10139136 log 512 len 38
2490453: expecting 10081280 actual extent phys 10141696 log 1024 len 365
2490455: expecting 10082304 actual extent phys 10143744 log 1024 len 288
2490457: expecting 10084352 actual extent phys 10144768 log 1024 len 251
2490460: expecting 10086400 actual extent phys 10145792 log 1024 len 166
2490462: expecting 10087424 actual extent phys 10146816 log 1
Are there other checks I should/can perform? Should I have formatted the
filesystem a different way? I followed the guide at
http://ext4.wiki.kernel.org/index.php/Ext4_Howto . This is not a
production system and needing to reformat is no big deal.
I googled around a bit only finding one post with fsck reporting over 100%
non contiguous. Could this be a bug?
Ideas?
--
Daryl Styrk
Naples FL, USA
Reply to: