(Samuel wrote)
There was a program called "e2defrag", but it was for ext2 only. e2fsck will give you a fragmentation percent at the end. Just don't forget the "-n" unless the partition is not mounted!
I done it. ----- -bash.5[~]: e2fsck -nf [partition] e2fsck 1.44.2 (14-May-2018) Warning! [partition] is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Deleted inode 52428804 has zero dtime. Fix? no
Inodes that were part of a corrupted orphan linked list found. Fix? no
Inode 52429073 was part of the orphaned inode list. IGNORED. Inode 52429167 was part of the orphaned inode list. IGNORED. Inode 52429328 was part of the orphaned inode list. IGNORED. Inode 52431131 was part of the orphaned inode list. IGNORED. Inode 52431332 was part of the orphaned inode list. IGNORED. Inode 52431496 was part of the orphaned inode list. IGNORED. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences: -33824 -(209757912--209757923) -(209759858--209759869) -(209766298--209766309) -(210052344--210052355) -(210616843--210616854) -(211515401--211515412) Fix? no
Free blocks count wrong (235056406, counted=235055939). Fix? no
Inode bitmap differences: -52428804 -52429073 -52429167 -52429328 -52431131 -52431332 -52431496 Fix? no
Free inodes count wrong (60127490, counted=60127428). Fix? no
[partition]: ********** WARNING: Filesystem still has errors **********
[partition]: 59134/60186624 files (1.7% non-contiguous), 5659882/240716288 blocks -bash.6[~]: ----- (hopefully, I got the right partition!) I gather the "1.7% non-contiguous" is what relates to fragmentation.
This does raise a few questions, but I'll deal with those late this month, in a separate thread, after I upgrade to F-29.
Thank-you, Samuel. Bill.