tools: Up version to 1.8.4

Signed-off-by: Srinivas Eeda <[email protected]>

scandisk: Add lookup for loop devices

This piece of code need to be fixed. It should pick a path based on
user configuration. Adding this hack for time being as the real fix
is still a work-in-progress.

Signed-off-by: Sunil Mushran <[email protected]>

ocfs2-tools: set or clear s_uuid_hash in tunefs.ocfs2

s_uuid_hash is used by two features indexed-dirs and xattr,
so set or clear it should concern the other feature's status.

Signed-off-by: Tiger Yang <[email protected]>
Acked-by: Sunil Mushran <[email protected]>
Acked-by: Mark Fasheh <[email protected]>

ocfs2-tools: o2hbmonitor moved to /usr/sbin

Signed-off-by: Sunil Mushran <[email protected]>

tools: Up version to 1.6.3

Signed-off-by: Sunil Mushran <[email protected]>
Signed-off-by: Joel Becker <[email protected]>

ocfs2-tools: Up version to 1.6.2

Signed-off-by: Sunil Mushran <[email protected]>

ocfs2-tools: Up version to 1.6.1

Signed-off-by: Sunil Mushran <[email protected]>

debugfs.ocfs2: stat shows inode's orphaned slot#

Include i_orphaned_slot when printing the inode.

Signed-off-by: Sunil Mushran <[email protected]>

mkfs.ocfs2: Print fs features during make

Patch makes mkfs.ocfs2 print the filesystem features being enabled.

Signed-off-by: Sunil Mushran <[email protected]>
Acked-by: Joel Becker <[email protected]>

debugfs.ocfs2: Add a fragmentation score to the 'frag' command.

Fragmentation is often looked at to see the effect on I/O.  But a 100%
fragmented file of 1MB clusters will perform a lot better than a 10%
fragmented file of 4K clusters.

This adds a 'fragmentation score' to the 'frag' command of
debugfs.ocfs2.  The score is simply calculated as the fragmentation
percentage times the number of clusters per megabyte.  Why a megabyte?
Partly because it's our largest cluster size, but also because we know
1MB I/Os are a nice sweet spot.

This gives us an easy way to compare the I/O of files across cluster
sizes.  The higher the score, the worse the I/O.

A file with one extent has a score of 0.  Our theoretical 100%
fragmented file of 1MB clusters has a score of 100.  The 10% fragmented
file of 4K clusters has a score of 2560.  Ouch!  That 10% fragmented
file has an average extent size of 40K.

Signed-off-by: Joel Becker <[email protected]>
Signed-off-by: Mark Fasheh <[email protected]>