On Wed, Apr 23, 2014 at 09:23:41AM +0200, Ivan Pantovic wrote: > > >[root@drive-b ~]# xfs_db -r /dev/md0 > >xfs_db> frag > >actual 11157932, ideal 11015175, fragmentation factor 1.28% > >xfs_db> > > this is current level of fragmentation ... is it bad? http://xfs.org/index.php/XFS_FAQ#Q:_The_xfs_db_.22frag.22_command_says_I.27m_over_50.25._Is_that_bad.3F > some say over 1% is candidate for defrag? ... Some say that over 70% is usually not a problem: http://www.mythtv.org/wiki/XFS_Filesystem#Defragmenting_XFS_Partitions i.e. the level that becomes are problem is highly workload specific. So, you can't read *anything* in that number without know exactly what is in your filesystem, how the application(s) interact with it and so on. Besides, I was asking specifically about the files you removed, not the files that remain in the filesystem. Given that you have 11 million inodes in the filesystem, you probably removed the only significantly large files in the filesystem.... So, the files your removed are now free space, so free space fragmentation is what we need to look at. i.e. use the freesp command to dump the histogram and summary of the free space... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
