Lines Matching full:the

3 .\" This file may be copied under the terms of the GNU Public License.
44 examine and change the state of an ext2, ext3, or ext4 file system.
47 is a block device (e.g., /dev/sdXX) or a file containing the file system.
51 Specifies that the file system should be opened in read-write mode.
52 Without this option, the file system is opened in read-only mode.
56 you believe the metadata to be correct despite the complaints of
60 Specifies that the file system should be opened in catastrophic mode, in
61 which the inode and group bitmaps are not read initially.  This can be
63 catastrophic mode forces the filesystem to be opened read-only.
68 represents an ext2 image file created by the
70 program.  Since the ext2 image file only contains the superblock, block
80 etc. are tried without specifying the
82 using the
89 Used with the
93 should be used when reading blocks not found in the ext2 image file.
97 Forces the use of the given block size (in bytes) for the file system,
98 rather than detecting the correct block size automatically.  (This
99 option is rarely needed; it is used primarily when the file system is
103 Causes the file system superblock to be read from the given block
104 number, instead of using the primary superblock (located at an offset of
105 1024 bytes from the beginning of the filesystem).  If you specify the
107 option, you must also provide the blocksize of the filesystem via the
110 option is rarely needed; it is used primarily when the file system is
125 to open the device using Direct I/O, bypassing the buffer cache.  Note
132 to execute the single command
137 print the version number of
142 Before overwriting a file system block, write the old contents of the block to
143 an undo file.  This undo file can be used with e2undo(8) to restore the old
144 contents of the file system should something go wrong.  If the empty string is
145 passed as the undo_file argument, the undo file will be written to a file named
146 resize2fs-\fIdevice\fR.e2undo in the directory specified via the
149 WARNING: The undo file cannot be used to recover from a power or system crash.
156 in the filesystem which is currently opened by
160 argument may be specified in two forms.  The first form is an inode
163 The second form is a pathname; if the pathname is prefixed by a forward slash
164 ('/'), then it is interpreted relative to the root of the filesystem
167 If not, the pathname is
168 interpreted relative to the current working directory as maintained by
170 This may be modified by using the
178 This is a list of the commands which
183 Print the blocks used by the inode
188 Print or set the physical block number corresponding to the logical block number
190 in the inode
192 If the
197 Dump the filesystem block given by
199 in hex and ASCII format to the console.  If the
201 option is specified, the block number is relative to the start of the given
205 Dump the contents of the inode
210 Change the current working directory to
214 Change the root directory to be the directory
218 Close the currently open file system.  If the
220 option is specified, write out any changes to the superblock and block
221 group descriptors to all of the backup superblocks, not just to the
225 Clear the contents of the inode
229 Copy the conents of the inode structure in
231 and use it to overwrite the inode structure at
235 Search the directory
241 Mark the filesystem as dirty, so that the superblocks will be written on exit.
244 Dump the contents of the inode
246 to the output file
248 If the
250 option is given set the owner, group and permissions information on
256 Display the multiple-mount protection (mmp) field values.  If
258 is specified then verify and dump the MMP values from the given block
259 number, otherwise use the
261 field in the superblock to locate and use the existing MMP block.
264 Calculate the directory hash of
275 Dump the the extent tree of the inode
281 to only display the interior nodes in the extent tree.   The
285 to only display the leaf nodes in the extent tree.
287 (Please note that the length and range of blocks for the last extent in
288 an interior node is an estimate by the extents library functions, and is
289 not stored in filesystem data structures.   Hence, the values displayed
291 corruption in the file system.)
294 Retrieve the value of the extended attribute
296 in the file
301 List the extended attributes associated with the file
306 Set the value of the extended attribute
308 in the file
310 to the string value
315 Remove the extended attribute
317 from the file \fIfilespec\fR.
320 Expand the directory
327 of free disk blocks or the maximum file size is reached.  Existing
331 Set or clear various filesystem features in the superblock.  After setting
332 or clearing any filesystem features that were requested, print the current
333 state of the filesystem feature set.
336 Print the number of contiguous extents in
340 is a directory and the
344 will print the number of contiguous extents for each file in
345 the directory.  The
349 print a tabular listing of the contiguous extents in the
350 file.  The
354 to do a recursive listing of the directory.
357 Find the first
367 specifies the inode number of the directory
368 which the inode is to be located.  The second
371 specifies the permissions of the new inode.  (If the directory bit is set
372 on the mode, the allocation routine will function differently.)  Also
377 Mark the block number
380 If the optional argument
389 Report free space fragmentation on the currently open file system.
390 If the
392 option is specified then the filefrag command will print how many free
395 can be found in the file system.  The chunk size must be a power of two
396 and be larger than the file system block size.
399 Free the inode specified by
403 is specified, also clear num-1 inodes after the specified inode.
410 Dump the hash-indexed directory
415 Print a listing of the inodes which use the one or more blocks specified
416 on the command line.
419 Print the contents of the inode data structure in hex and ASCII format.
422 Print the location of the inode data structure (in the inode table)
423 of the inode
431 Note that this does not fully initialize all of the data structures;
432 to do this, use the
434 program.  This is just a call to the low-level library, which sets up
438 Close the open journal.
441 Opens the journal for reading and writing.  Journal checksumming can
443 selected with the \fI-v\fR option.  An external journal can be loaded
447 Replay all transactions in the open journal.
450 Write a transaction to the open journal.  The list of blocks to write
451 should be supplied as a comma-separated list in \fIblocks\fR; the
454 \fIrevoke\fR.  By default, a commit record is written at the end; the
458 Deallocate the inode
461 entries (if any) to this inode.  See the
466 Change the current working directory of the
470 on the native filesystem.
477 Note this does not adjust the inode reference counts.
480 Dump the contents of the ext3 journal.  By default, dump the journal inode as
481 specified in the superblock.  However, this can be overridden with the
483 option, which dumps the journal from the internal inode given by
485 A regular file containing journal data can be specified using the
487 option.  Finally, the
489 option utilizes the backup information in the superblock to locate the
494 option causes the
496 program to print the contents of all of the descriptor blocks.
501 to print all journal records that are refer to the specified block.
504 option will print out the contents of all of the data blocks selected by
514 This can be used to try to track down journal problems even after the
518 Print a listing of the files in the directory
525 flag will list deleted entries in the directory.
531 flag will list the files in a format which is more easily parsable by
533 non-printing characters at the end of filenames.
536 flag will force the printing of the filename, even if it is encrypted.
546 if the files were deleted using ext3 or ext4, since the inode's
547 data blocks are no longer available after the inode is released.
550 Modify the contents of the inode structure in the inode
560 If a character or block device is to be made, the
567 Take the requested list of inode numbers, and print a listing of pathnames
568 to those inodes.  The
570 flag will enable checking the file type information in the directory
571 entry to make sure it matches the inode's type.
574 Open a filesystem for editing.  The
576 flag forces the filesystem to be opened even if there are some unknown
578 prevent the filesystem from being opened.  The
580 flag causes the filesystem to be opened in exclusive mode.  The
582 options behave the same as the command-line options to
586 Delete the blocks in the inode ranging from
593 is, all of the blocks starting at
595 through to the end of the file will be deallocated.
601 Print the current working directory.
613 directories) into the named
615 which should be an existing directory on the native filesystem.
620 If this causes the inode pointed to by
622 to have no other references, deallocate the file.  This command functions
623 as the unlink() system call.
627 Remove the directory
631 Mark the block number
634 If the optional argument
643 Modify the block group descriptor specified by
645 so that the block group descriptor field
655 as in use in the inode bitmap.  If
657 is specified, also set num-1 inodes after the specified inode.
660 Modify the inode specified by
662 so that the inode field
667 can be displayed by using the command:
673 Modify the multiple-mount protection (MMP) data so that the MMP field
678 can be displayed by using the command:
684 Set the superblock field
689 can be displayed by using the command:
695 List the contents of the super block and the block group descriptors.  If the
697 flag is given, only print out the superblock contents. Also available as
701 Display the contents of the inode structure of the inode
705 Test if the block number
707 is marked as allocated in the block bitmap.
708 If the optional argument
717 Test if the inode
719 is marked as allocated in the inode bitmap.
722 Undelete the specified inode number (which must be surrounded by angle
724 link the recovered inode to the specified pathname.  The
726 command should always be run after using the
731 the inode to a directory may require the directory to be expanded, which
732 could allocate a block that had been used by one of the
733 yet-to-be-undeleted files.  So it is safer to undelete all of the
735 pass, use the debugfs
737 command to link the inode to the destination pathname, or use
739 to check the filesystem and link all of the recovered inodes to the
743 Remove the link specified by
745 to an inode.  Note this does not adjust the inode reference counts.
748 Copy the contents of
750 into a newly-created file in the filesystem named
754 Overwrite the block specified by
758 is given use the byte specified by
764 is relative to the start of the file given by
770 options limit the range of bytes to zap to the specified
774 relative to the start of the block.
777 Bit-flip portions of the physical
783 is a logical block relative to the start of
790 program always pipes the output of the some commands through a
798 The specific pager can explicitly specified by the
800 environment variable, and if it is not set, by the
804 Note that since a pager is always used, the
806 pager is not particularly appropriate, since it clears the screen before
807 displaying the output of the command and clears the output the screen
808 when the pager is exited.  Many users prefer to use the
810 pager for most purposes, which is why the
812 environment variable is available to override the more general