FILEFRAG(8) System Manager's Manual FILEFRAG(8)NAME
filefrag - report on file fragmentation
SYNOPSIS
filefrag [ -Bbsvx ] [ files... ]
DESCRIPTION
filefrag reports on how badly fragmented a particular file might be. It makes allowances for indirect blocks for ext2 and ext3 filesys-
tems, but can be used on files for any filesystem.
The filefrag program initially attempts to get the extent information using FIEMAP ioctl which is more efficient and faster. If FIEMAP is
not supported then filefrag will fall back to using FIBMAP.
OPTIONS -B Force the use of the older FIBMAP ioctl instead of the FIEMAP ioctl for testing purposes.
-b Use 1024 byte blocksize for the output.
-s Sync the file before requesting the mapping.
-v Be verbose when checking for file fragmentation.
-x Display mapping of extended attributes.
AUTHOR
filefrag was written by Theodore Ts'o <tytso@mit.edu>.
E2fsprogs version 1.41.11 March 2010 FILEFRAG(8)
Check Out this Related Man Page
DUMPE2FS(8) System Manager's Manual DUMPE2FS(8)NAME
dumpe2fs - dump ext2/ext3/ext4 filesystem information
SYNOPSIS
dumpe2fs [ -bfhixV ] [ -o superblock=superblock ] [ -o blocksize=blocksize ] device
DESCRIPTION
dumpe2fs prints the super block and blocks group information for the filesystem present on device.
Note: When used with a mounted filesystem, the printed information may be old or inconsistent.
OPTIONS -b print the blocks which are reserved as bad in the filesystem.
-o superblock=superblock
use the block superblock when examining the filesystem. This option is not usually needed except by a filesystem wizard who is
examining the remains of a very badly corrupted filesystem.
-o blocksize=blocksize
use blocks of blocksize bytes when examining the filesystem. This option is not usually needed except by a filesystem wizard who is
examining the remains of a very badly corrupted filesystem.
-f force dumpe2fs to display a filesystem even though it may have some filesystem feature flags which dumpe2fs may not understand (and
which can cause some of dumpe2fs's display to be suspect).
-h only display the superblock information and not any of the block group descriptor detail information.
-i display the filesystem data from an image file created by e2image, using device as the pathname to the image file.
-x print the detailed group information block numbers in hexadecimal format
-V print the version number of dumpe2fs and exit.
BUGS
You need to know the physical filesystem structure to understand the output.
AUTHOR
dumpe2fs was written by Remy Card <Remy.Card@linux.org>. It is currently being maintained by Theodore Ts'o <tytso@alum.mit.edu>.
AVAILABILITY
dumpe2fs is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net.
SEE ALSO e2fsck(8), mke2fs(8), tune2fs(8)E2fsprogs version 1.42.5 July 2012 DUMPE2FS(8)
When we write a programme,we declare variables and compiler allocates memory to them.I want to get access to the physical block number of hard-disk where actually the data is stored by the programme "
Some one help me out... (3 Replies)
Hi,
I am trying to measure the speed of reading a given block size using the dd command. However depending on which input I use: a regular file (on the same device) or /dev/sdb1, I get some really different results.
$sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; dd if=pirate of=/dev/null... (9 Replies)
Is there any way to translate a file name to the underlying file system's disk blocks/sectors/extents on UFS (Solaris OS on Sparc)?
I found several ways to do it on linux file systems like ext2/3/4, using command like hdparm -- fibmap and filefrag.
I also found one equivalent way to get that... (9 Replies)