Lines Matching full:the
3 .\" This file may be copied under the terms of the GNU Public License.
40 examine and change the state of an ext2, ext3, or ext4 file system.
43 is the special file corresponding to the device containing the
48 Specifies that the file system should be opened in read-write mode.
49 Without this option, the file system is opened in read-only mode.
52 Specifies that the file system should be opened in catastrophic mode, in
53 which the inode and group bitmaps are not read initially. This can be
55 catastrophic mode forces the filesystem to be opened read-only.
60 represents an ext2 image file created by the
62 program. Since the ext2 image file only contains the superblock, block
72 etc. are tried without specifying the
74 using the
81 Used with the
85 should be used when reading blocks not found in the ext2 image file.
89 Forces the use of the given block size for the file system, rather than
90 detecting the correct block size as normal.
93 Causes the file system superblock to be read from the given block
94 number, instead of using the primary superblock (located at an offset of
95 1024 bytes from the beginning of the filesystem). If you specify the
97 option, you must also provide the blocksize of the filesystem via the
113 to open the device using Direct I/O, bypassing the buffer cache. Note
120 to execute the single command
125 print the version number of
134 in the filesystem which is currently opened by
138 argument may be specified in two forms. The first form is an inode
141 The second form is a pathname; if the pathname is prefixed by a forward slash
142 ('/'), then it is interpreted relative to the root of the filesystem
145 If not, the pathname is
146 interpreted relative to the current working directory as maintained by
148 This may be modified by using the
156 This is a list of the commands which
161 Print the blocks used by the inode
166 Print the physical block number corresponding to the logical block number
168 in the inode
172 Dump the filesystem block given by
174 in hex and ASCII format to the console. If the
176 option is specified, the block number is relative to the start of the given
180 Dump the contents of the inode
185 Change the current working directory to
189 Change the root directory to be the directory
193 Close the currently open file system. If the
195 option is specified, write out any changes to the superblock and block
196 group descriptors to all of the backup superblocks, not just to the
200 Clear the contents of the inode
204 Search the directory
210 Mark the filesystem as dirty, so that the superblocks will be written on exit.
213 Dump the contents of the inode
215 to the output file
217 If the
219 option is given set the owner, group and permissions information on
225 Display the multiple-mount protection (mmp) field values.
228 Calculate the directory hash of
239 Dump the the extent tree of the inode
245 to only display the interior nodes in the extent tree. The
249 to only display the leaf nodes in the extent tree.
251 (Please note that the length and range of blocks for the last extent in
252 an interior node is an estimate by the extents library functions, and is
253 not stored in filesystem data structures. Hence, the values displayed
255 corruption in the file system.)
258 Expand the directory
262 Set or clear various filesystem features in the superblock. After setting
263 or clearing any filesystem features that were requested, print the current
264 state of the filesystem feature set.
267 Print the number of contiguous extents in
271 is a directory and the
275 will print the number of contiguous extents for each file in
276 the directory. The
280 print a tabular listing of the contiguous extents in the
281 file. The
285 to do a recursive listing of the directory.
288 Find the first
298 specifies the inode number of the directory
299 which the inode is to be located. The second
302 specifies the permissions of the new inode. (If the directory bit is set
303 on the mode, the allocation routine will function differently.) Also
308 Mark the block number
311 If the optional argument
320 Report free space fragmentation on the currently open file system.
321 If the
323 option is specified then the filefrag command will print how many free
326 can be found in the file system. The chunk size must be a power of two
327 and be larger than the file system block size.
330 Free the inode specified by
334 is specified, also clear num-1 inodes after the specified inode.
341 Dump the hash-indexed directory
346 Print a listing of the inodes which use the one or more blocks specified
347 on the command line.
350 Print the location of the inode data structure (in the inode table)
351 of the inode
359 Note that this does not fully initialize all of the data structures;
360 to do this, use the
362 program. This is just a call to the low-level library, which sets up
366 Deallocate the inode
369 entries (if any) to this inode. See the
374 Change the current working directory of the
378 on the native filesystem.
385 Note this does not adjust the inode reference counts.
388 Dump the contents of the ext3 journal. By default, dump the journal inode as
389 specified in the superblock. However, this can be overridden with the
391 option, which dumps the journal from the internal inode given by
393 A regular file containing journal data can be specified using the
395 option. Finally, the
397 option utilizes the backup information in the superblock to locate the
402 option causes the
404 program to print the contents of all of the descriptor blocks.
409 to print all journal records that are refer to the specified block.
412 option will print out the contents of all of the data blocks selected by
420 Print a listing of the files in the directory
424 flag will list deleted entries in the directory.
430 flag will list the files in a format which is more easily parsable by
432 non-printing characters at the end of filenames.
442 if the files were deleted using ext3 or ext4, since the inode's
443 data blocks are no longer available after the inode is released.
446 Modify the contents of the inode structure in the inode
456 If a character or block device is to be made, the
463 Take the requested list of inode numbers, and print a listing of pathnames
464 to those inodes. The
466 flag will enable checking the file type information in the directory
467 entry to make sure it matches the inode's type.
470 Open a filesystem for editing. The
472 flag forces the filesystem to be opened even if there are some unknown
474 prevent the filesystem from being opened. The
476 flag causes the filesystem to be opened in exclusive mode. The
478 options behave the same as the command-line options to
482 Delete the blocks in the inode ranging from
489 is, all of the blocks starting at
491 through to the end of the file will be deallocated.
497 Print the current working directory.
507 directories) into the named
509 which should be an existing directory on the native filesystem.
514 If this causes the inode pointed to by
516 to have no other references, deallocate the file. This command functions
517 as the unlink() system call.
521 Remove the directory
525 Mark the block number
528 If the optional argument
537 Modify the block group descriptor specified by
539 so that the block group descriptor field
549 as in use in the inode bitmap. If
551 is specified, also set num-1 inodes after the specified inode.
554 Modify the inode specified by
556 so that the inode field
561 can be displayed by using the command:
567 Modify the multiple-mount protection (MMP) data so that the MMP field
572 can be displayed by using the command:
578 Set the superblock field
583 can be displayed by using the command:
589 List the contents of the super block and the block group descriptors. If the
591 flag is given, only print out the superblock contents. Also available as
595 Display the contents of the inode structure of the inode
599 Test if the block number
601 is marked as allocated in the block bitmap.
602 If the optional argument
611 Test if the inode
613 is marked as allocated in the inode bitmap.
616 Undelete the specified inode number (which must be surrounded by angle
618 link the recovered inode to the specified pathname. The
620 command should always be run after using the
625 the inode to a directory may require the directory to be expanded, which
626 could allocate a block that had been used by one of the
627 yet-to-be-undeleted files. So it is safer to undelete all of the
629 pass, use the debugfs
631 command to link the inode to the destination pathname, or use
633 to check the filesystem and link all of the recovered inodes to the
637 Remove the link specified by
639 to an inode. Note this does not adjust the inode reference counts.
642 Copy the contents of
644 into a newly-created file in the filesystem named
649 Overwrite the block specified by
653 is given use the byte specified by
659 is relative to the start of the file given by
665 options limit the range of bytes to zap to the specified
669 relative to the start of the block.
672 Bit-flip portions of the physical
678 is a logical block relative to the start of
685 program always pipes the output of the some commands through a
693 The specific pager can explicitly specified by the
695 environment variable, and if it is not set, by the
699 Note that since a pager is always used, the
701 pager is not particularly appropriate, since it clears the screen before
702 displaying the output of the command and clears the output the screen
703 when the pager is exited. Many users prefer to use the
705 pager for most purposes, which is why the
707 environment variable is available to override the more general