Blame SOURCES/xfsprogs-4.7.0-defang-frag.patch

9bf599
commit 027e6efd2b432232562d726f14702f79792b38cb
9bf599
Author: Eric Sandeen <sandeen@sandeen.net>
9bf599
Date:   Mon May 30 10:35:56 2016 +1000
9bf599
9bf599
    xfs_db: defang frag command
9bf599
    
9bf599
    Too many people freak out about this fictitious "fragmentation
9bf599
    factor."  As shown in the fact, it is largely meaningless, because
9bf599
    the number approaches 100% extremely quickly for just a few
9bf599
    extents per file.
9bf599
    
9bf599
    I thought about removing it altogether, but perhaps a note
9bf599
    about its uselessness, and a more soothing metric (avg extents
9bf599
    per file) might be useful.
9bf599
    
9bf599
    Signed-off-by: Eric Sandeen <sandeen@redhat.com>
9bf599
    Reviewed-by: Christoph Hellwig <hch@lst.de>
9bf599
    Signed-off-by: Dave Chinner <david@fromorbit.com>
9bf599
9bf599
Index: xfsprogs-4.5.0/db/frag.c
9bf599
===================================================================
9bf599
--- xfsprogs-4.5.0.orig/db/frag.c
9bf599
+++ xfsprogs-4.5.0/db/frag.c
9bf599
@@ -172,6 +172,10 @@ frag_f(
9bf599
 		answer = 0.0;
9bf599
 	dbprintf(_("actual %llu, ideal %llu, fragmentation factor %.2f%%\n"),
9bf599
 		extcount_actual, extcount_ideal, answer);
9bf599
+	dbprintf(_("Note, this number is largely meaningless.\n"));
9bf599
+	answer = (double)extcount_actual / (double)extcount_ideal;
9bf599
+	dbprintf(_("Files on this filesystem average %.2f extents per file\n"),
9bf599
+		answer);
9bf599
 	return 0;
9bf599
 }
9bf599