{"id":3127,"date":"2022-12-20T16:43:33","date_gmt":"2022-12-20T19:43:33","guid":{"rendered":"http:\/\/lode.uno\/linux-man\/index.php\/2022\/12\/20\/debugfs-man8\/"},"modified":"2022-12-20T16:43:33","modified_gmt":"2022-12-20T19:43:33","slug":"debugfs-man8","status":"publish","type":"post","link":"https:\/\/lode.uno\/linux-man\/2022\/12\/20\/debugfs-man8\/","title":{"rendered":"DEBUGFS (man8)"},"content":{"rendered":"

DEBUGFS<\/h1>\n

NAME<\/a>
SYNOPSIS<\/a>
DESCRIPTION<\/a>
OPTIONS<\/a>
SPECIFYING FILES<\/a>
COMMANDS<\/a>
ENVIRONMENT VARIABLES<\/a>
AUTHOR<\/a>
SEE ALSO<\/a> <\/p>\n

\n

NAME <\/a> <\/h2>\n

debugfs \u2212 ext2\/ext3\/ext4 file system debugger<\/p>\n

SYNOPSIS <\/a> <\/h2>\n

debugfs<\/b> [ \u2212DVwcin<\/b> ] [ \u2212b<\/b> blocksize ] [ \u2212s<\/b> superblock ] [ \u2212f<\/b> cmd_file ] [ \u2212R<\/b> request ] [ \u2212d<\/b> data_source_device ] [ \u2212z<\/b> undo_file<\/i> ] [ device ]<\/p>\n

DESCRIPTION <\/a> <\/h2>\n

The debugfs<\/b> program is an interactive file system debugger. It can be used to examine and change the state of an ext2, ext3, or ext4 file system.<\/p>\n

device<\/i> is a block device (e.g., \/dev\/sdXX) or a file containing the file system.<\/p>\n

OPTIONS <\/a> <\/h2>\n\n\n\n\n\n
<\/td>\n\n

\u2212w<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Specifies that the file system should be opened in read-write mode. Without this option, the file system is opened in read-only mode.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212n<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Disables metadata checksum verification. This should only be used if you believe the metadata to be correct despite the complaints of e2fsprogs.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212c<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Specifies that the file system should be opened in catastrophic mode, in which the inode and group bitmaps are not read initially. This can be useful for filesystems with significant corruption, but because of this, catastrophic mode forces the filesystem to be opened read-only.<\/p>\n<\/td>\n<\/tr>\n

<\/td>\n\n

\u2212i<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Specifies that device<\/i> represents an ext2 image file created by the e2image<\/b> program. Since the ext2 image file only contains the superblock, block group descriptor, block and inode allocation bitmaps, and the inode table, many debugfs<\/b> commands will not function properly. Warning:<\/b> no safety checks are in place, and debugfs<\/b> may fail in interesting ways if commands such as ls<\/i>, dump<\/i>, etc. are tried without specifying the data_source_device<\/i> using the \u2212d<\/i> option. debugfs<\/b> is a debugging tool. It has rough edges!<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

-d data_source_device<\/i><\/p>\n

Used with the \u2212i<\/i> option, specifies that data_source_device<\/i> should be used when reading blocks not found in the ext2 image file. This includes data, directory, and indirect blocks.<\/p>\n

-b blocksize<\/i><\/p>\n

Forces the use of the given block size (in bytes) for the file system, rather than detecting the correct block size automatically. (This option is rarely needed; it is used primarily when the file system is extremely badly damaged\/corrupted.)<\/p>\n

-s superblock<\/i><\/p>\n

Causes the file system superblock to be read from the given block number, instead of using the primary superblock (located at an offset of 1024 bytes from the beginning of the filesystem). If you specify the -s<\/i> option, you must also provide the blocksize of the filesystem via the -b<\/i> option. (This option is rarely needed; it is used primarily when the file system is extremely badly damaged\/corrupted.)<\/p>\n

-f cmd_file<\/i><\/p>\n

Causes debugfs<\/b> to read in commands from cmd_file<\/i>, and execute them. When debugfs<\/b> is finished executing those commands, it will exit.<\/p>\n\n\n
<\/td>\n\n

-D<\/i><\/p>\n<\/td>\n

<\/td>\n\n

Causes debugfs<\/b> to open the device using Direct I\/O, bypassing the buffer cache. Note that some Linux devices, notably device mapper as of this writing, do not support Direct I\/O.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n

-R request<\/i><\/p>\n

Causes debugfs<\/b> to execute the single command request<\/i>, and then exit.<\/p>\n\n\n
<\/td>\n\n

-V<\/i><\/p>\n<\/td>\n

<\/td>\n\n

print the version number of debugfs<\/b> and exit.<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

\u2212z<\/b> undo_file<\/i><\/p>\n

Before overwriting a file system block, write the old contents of the block to an undo file. This undo file can be used with e2undo(8) to restore the old contents of the file system should something go wrong. If the empty string is passed as the undo_file argument, the undo file will be written to a file named debugfs-device<\/i>.e2undo in the directory specified via the E2FSPROGS_UNDO_DIR<\/i> environment variable.<\/p>\n

WARNING: The undo file cannot be used to recover from a power or system crash.<\/p>\n

SPECIFYING FILES <\/a> <\/h2>\n

Many debugfs<\/b> commands take a filespec<\/i> as an argument to specify an inode (as opposed to a pathname) in the filesystem which is currently opened by debugfs<\/b>. The filespec<\/i> argument may be specified in two forms. The first form is an inode number surrounded by angle brackets, e.g., <2><\/i>. The second form is a pathname; if the pathname is prefixed by a forward slash (\u2019\/\u2019), then it is interpreted relative to the root of the filesystem which is currently opened by debugfs<\/b>. If not, the pathname is interpreted relative to the current working directory as maintained by debugfs<\/b>. This may be modified by using the debugfs<\/b> command cd<\/i>.<\/p>\n

COMMANDS <\/a> <\/h2>\n

This is a list of the commands which debugfs<\/b> supports.
blocks<\/b> filespec<\/i><\/p>\n

Print the blocks used by the inode filespec<\/i> to stdout.<\/p>\n

bmap<\/b> [ -a ] filespec logical_block [physical_block]<\/i><\/p>\n

Print or set the physical block number corresponding to the logical block number logical_block<\/i> in the inode filespec<\/i>. If the \u2212a<\/i> flag is specified, try to allocate a block if necessary.<\/p>\n

block_dump<\/b> \u2019[ -x ] [-f filespec] block_num<\/i><\/p>\n

Dump the filesystem block given by block_num<\/i> in hex and ASCII format to the console. If the \u2212f<\/i> option is specified, the block number is relative to the start of the given filespec<\/b>. If the \u2212x<\/i> option is specified, the block is interpreted as an extended attribute block and printed to show the structure of extended attribute data structures.<\/p>\n

cat<\/b> filespec<\/i><\/p>\n

Dump the contents of the inode filespec<\/i> to stdout.<\/p>\n

cd<\/b> filespec<\/i><\/p>\n

Change the current working directory to filespec<\/i>.<\/p>\n

chroot<\/b> filespec<\/i><\/p>\n

Change the root directory to be the directory filespec<\/i>.<\/p>\n

close<\/b> [-a]<\/i><\/p>\n

Close the currently open file system. If the -a<\/i> option is specified, write out any changes to the superblock and block group descriptors to all of the backup superblocks, not just to the master superblock.<\/p>\n

clri<\/b> filespec<\/i><\/p>\n

Clear the contents of the inode filespec<\/i>.<\/p>\n

copy_inode<\/b> source_inode destination_inode<\/i><\/p>\n

Copy the contents of the inode structure in source_inode<\/i> and use it to overwrite the inode structure at destination_inode<\/i>.<\/p>\n

dirsearch<\/b> filespec filename<\/i><\/p>\n

Search the directory filespec<\/i> for filename<\/i>.<\/p>\n

dirty<\/b> [-clean]<\/i><\/p>\n

Mark the filesystem as dirty, so that the superblocks will be written on exit. Additionally, clear the superblock\u2019s valid flag, or set it if -clean<\/i> is specified.<\/p>\n

dump<\/b> [-p] filespec out_file<\/i><\/p>\n

Dump the contents of the inode filespec<\/i> to the output file out_file<\/i>. If the -p<\/i> option is given set the owner, group and permissions information on out_file<\/i> to match filespec<\/i>.<\/p>\n

dump_mmp<\/b> [mmp_block]<\/i><\/p>\n

Display the multiple-mount protection (mmp) field values. If mmp_block<\/i> is specified then verify and dump the MMP values from the given block number, otherwise use the s_mmp_block<\/b> field in the superblock to locate and use the existing MMP block.<\/p>\n

dx_hash<\/b> [-h hash_alg] [-s hash_seed] filename<\/i><\/p>\n

Calculate the directory hash of filename<\/i>. The hash algorithm specified with -h<\/i> may be legacy<\/b>, half_md4<\/b>, or tea<\/b>. The hash seed specified with -s<\/i> must be in UUID format.<\/p>\n

dump_extents<\/b> [-n] [-l] filespec<\/i><\/p>\n

Dump the the extent tree of the inode filespec<\/i>. The -n<\/i> flag will cause dump_extents<\/b> to only display the interior nodes in the extent tree. The -l<\/i> flag will cause dump_extents<\/b> to only display the leaf nodes in the extent tree.<\/p>\n

(Please note that the length and range of blocks for the last extent in an interior node is an estimate by the extents library functions, and is not stored in filesystem data structures. Hence, the values displayed may not necessarily by accurate and does not indicate a problem or corruption in the file system.)<\/p>\n

dump_unused<\/b><\/p>\n

Dump unused blocks which contain non-null bytes.<\/p>\n

ea_get<\/b> [-f outfile]|[-xVC] [-r] filespec attr_name<\/i><\/p>\n

Retrieve the value of the extended attribute attr_name<\/i> in the file filespec<\/i> and write it either to stdout or to outfile<\/i>.<\/p>\n

ea_list<\/b> filespec<\/i><\/p>\n

List the extended attributes associated with the file filespec<\/i> to standard output.<\/p>\n

ea_set<\/b> [-f infile] [-r] filespec attr_name attr_value<\/i><\/p>\n

Set the value of the extended attribute attr_name<\/i> in the file filespec<\/i> to the string value attr_value<\/i> or read it from infile<\/i>.<\/p>\n

ea_rm<\/b> filespec attr_names…<\/i><\/p>\n

Remove the extended attribute attr_name<\/i> from the file filespec<\/i>.<\/p>\n

expand_dir<\/b> filespec<\/i><\/p>\n

Expand the directory filespec<\/i>.<\/p>\n

fallocate<\/b> filespec start_block [end_block]<\/i><\/p>\n

Allocate and map uninitialized blocks into filespec<\/i> between logical block start_block<\/i> and end_block<\/i>, inclusive. If end_block<\/i> is not supplied, this function maps until it runs out of free disk blocks or the maximum file size is reached. Existing mappings are left alone.<\/p>\n

feature<\/b> [fs_feature] [-fs_feature] …<\/i><\/p>\n

Set or clear various filesystem features in the superblock. After setting or clearing any filesystem features that were requested, print the current state of the filesystem feature set.<\/p>\n

filefrag<\/b> [-dvr] filespec<\/i><\/p>\n

Print the number of contiguous extents in filespec<\/i>. If filespec<\/i> is a directory and the -d<\/i> option is not specified, filefrag<\/i> will print the number of contiguous extents for each file in the directory. The -v<\/i> option will cause filefrag<\/i> print a tabular listing of the contiguous extents in the file. The -r<\/i> option will cause filefrag<\/i> to do a recursive listing of the directory.<\/p>\n

find_free_block<\/b> [count [goal]]<\/i><\/p>\n

Find the first count<\/i> free blocks, starting from goal<\/i> and allocate it. Also available as ffb<\/b>.<\/p>\n

find_free_inode<\/b> [dir [mode]]<\/i><\/p>\n

Find a free inode and allocate it. If present, dir<\/i> specifies the inode number of the directory which the inode is to be located. The second optional argument mode<\/i> specifies the permissions of the new inode. (If the directory bit is set on the mode, the allocation routine will function differently.) Also available as ffi<\/b>.<\/p>\n

freeb<\/b> block [count]<\/i><\/p>\n

Mark the block number block<\/i> as not allocated. If the optional argument count<\/i> is present, then count<\/i> blocks starting at block number block<\/i> will be marked as not allocated.<\/p>\n

freefrag<\/b> [-c chunk_kb]<\/i><\/p>\n

Report free space fragmentation on the currently open file system. If the \u2212c<\/i> option is specified then the filefrag command will print how many free chunks of size chunk_kb<\/i> can be found in the file system. The chunk size must be a power of two and be larger than the file system block size.<\/p>\n

freei<\/b> filespec [num]<\/i><\/p>\n

Free the inode specified by filespec<\/i>. If num<\/i> is specified, also clear num-1 inodes after the specified inode.<\/p>\n

get_quota<\/b> quota_type id<\/i><\/p>\n

Display quota information for given quota type (user, group, or project) and ID.<\/p>\n\n\n
<\/td>\n\n

help<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print a list of commands understood by debugfs<\/b>.<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

htree_dump<\/b> filespec<\/i><\/p>\n

Dump the hash-indexed directory filespec<\/i>, showing its tree structure.<\/p>\n

icheck<\/b> block …<\/i><\/p>\n

Print a listing of the inodes which use the one or more blocks specified on the command line.<\/p>\n

inode_dump<\/b> [-b]|[-e]|[-x] filespec<\/i><\/p>\n

Print the contents of the inode data structure in hex and ASCII format. The \u2212b<\/i> option causes the command to only dump the contents of the i_blocks<\/b> array. The \u2212e<\/i> option causes the command to only dump the contents of the extra inode space, which is used to store in-line extended attributes. The \u2212x<\/i> option causes the command to dump the extra inode space interpreted and extended attributes. This is useful to debug corrupted inodes containing extended attributes.<\/p>\n

imap<\/b> filespec<\/i><\/p>\n

Print the location of the inode data structure (in the inode table) of the inode filespec<\/i>.<\/p>\n

init_filesys<\/b> device blocksize<\/i><\/p>\n

Create an ext2 file system on device<\/i> with device size blocksize<\/i>. Note that this does not fully initialize all of the data structures; to do this, use the mke2fs<\/b>(8) program. This is just a call to the low-level library, which sets up the superblock and block descriptors.<\/p>\n

journal_close<\/b><\/p>\n

Close the open journal.<\/p>\n

journal_open<\/b> [-c] [-v ver] [-f ext_jnl]<\/i><\/p>\n

Opens the journal for reading and writing. Journal checksumming can be enabled by supplying -c<\/i>; checksum formats 2 and 3 can be selected with the -v<\/i> option. An external journal can be loaded from ext_jnl<\/i>.<\/p>\n

journal_run<\/b><\/p>\n

Replay all transactions in the open journal.<\/p>\n

journal_write<\/b> [-b blocks] [-r revoke] [-c] file<\/i><\/p>\n

Write a transaction to the open journal. The list of blocks to write should be supplied as a comma-separated list in blocks<\/i>; the blocks themselves should be readable from file<\/i>. A list of blocks to revoke can be supplied as a comma-separated list in revoke<\/i>. By default, a commit record is written at the end; the -c<\/i> switch writes an uncommitted transaction.<\/p>\n

kill_file<\/b> filespec<\/i><\/p>\n

Deallocate the inode filespec<\/i> and its blocks. Note that this does not remove any directory entries (if any) to this inode. See the rm<\/b>(1) command if you wish to unlink a file.<\/p>\n

lcd<\/b> directory<\/i><\/p>\n

Change the current working directory of the debugfs<\/b> process to directory<\/i> on the native filesystem.<\/p>\n

list_quota<\/b> quota_type<\/i><\/p>\n

Display quota information for given quota type (user, group, or project).<\/p>\n

ln<\/b> filespec dest_file<\/i><\/p>\n

Create a link named dest_file<\/i> which is a hard link to filespec<\/i>. Note this does not adjust the inode reference counts.<\/p>\n

logdump<\/b> [-acsOS] [-b block] [-i filespec] [-f journal_file]
[output_file]<\/i><\/p>\n

Dump the contents of the ext3 journal. By default, dump the journal inode as specified in the superblock. However, this can be overridden with the \u2212i<\/i> option, which dumps the journal from the internal inode given by filespec<\/i>. A regular file containing journal data can be specified using the \u2212f<\/i> option. Finally, the \u2212s<\/i> option utilizes the backup information in the superblock to locate the journal.<\/p>\n

The \u2212S<\/i> option causes logdump<\/b> to print the contents of the journal superblock.<\/p>\n

The \u2212a<\/i> option causes the logdump<\/b> program to print the contents of all of the descriptor blocks. The \u2212b<\/i> option causes logdump<\/b> to print all journal records that refer to the specified block. The \u2212c<\/i> option will print out the contents of all of the data blocks selected by the \u2212a<\/i> and \u2212b<\/i> options.<\/p>\n

The \u2212O<\/i> option causes logdump to display old (checkpointed) journal entries. This can be used to try to track down journal problems even after the journal has been replayed.<\/p>\n

ls<\/b> [-l] [-c] [-d] [-p] [-r] filespec<\/i><\/p>\n

Print a listing of the files in the directory filespec<\/i>. The \u2212c<\/i> flag causes directory block checksums (if present) to be displayed. The \u2212d<\/i> flag will list deleted entries in the directory. The \u2212l<\/i> flag will list files using a more verbose format. The \u2212p<\/i> flag will list the files in a format which is more easily parsable by scripts, as well as making it more clear when there are spaces or other non-printing characters at the end of filenames. The \u2212r<\/i> flag will force the printing of the filename, even if it is encrypted.<\/p>\n

list_deleted_inodes<\/b> [limit]<\/i><\/p>\n

List deleted inodes, optionally limited to those deleted within limit<\/i> seconds ago. Also available as lsdel<\/b>.<\/p>\n

This command was useful for recovering from accidental file deletions for ext2 file systems. Unfortunately, it is not useful for this purpose if the files were deleted using ext3 or ext4, since the inode\u2019s data blocks are no longer available after the inode is released.<\/p>\n

modify_inode<\/b> filespec<\/i><\/p>\n

Modify the contents of the inode structure in the inode filespec<\/i>. Also available as mi<\/b>.<\/p>\n

mkdir<\/b> filespec<\/i><\/p>\n

Make a directory.<\/p>\n

mknod<\/b> filespec [p|[[c|b] major minor]]<\/i><\/p>\n

Create a special device file (a named pipe, character or block device). If a character or block device is to be made, the major<\/i> and minor<\/i> device numbers must be specified.<\/p>\n

ncheck<\/b> [-c] inode_num …<\/i><\/p>\n

Take the requested list of inode numbers, and print a listing of pathnames to those inodes. The -c<\/i> flag will enable checking the file type information in the directory entry to make sure it matches the inode\u2019s type.<\/p>\n

open<\/b> [-weficD] [-b blocksize] [-d image_filename] [-s superblock] [-z
undo_file] device<\/i><\/p>\n

Open a filesystem for editing. The -f<\/i> flag forces the filesystem to be opened even if there are some unknown or incompatible filesystem features which would normally prevent the filesystem from being opened. The -e<\/i> flag causes the filesystem to be opened in exclusive mode. The -b<\/i>, -c<\/i>, -d<\/i>, -i<\/i>, -s<\/i>, -w<\/i>, and -D<\/i> options behave the same as the command-line options to debugfs<\/b>.<\/p>\n

punch<\/b> filespec start_blk [end_blk]<\/i><\/p>\n

Delete the blocks in the inode ranging from start_blk<\/i> to end_blk<\/i>. If end_blk<\/i> is omitted then this command will function as a truncate command; that is, all of the blocks starting at start_blk<\/i> through to the end of the file will be deallocated.<\/p>\n

symlink<\/b> filespec target<\/i><\/p>\n

Make a symbolic link.<\/p>\n\n\n\n
<\/td>\n\n

pwd<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Print the current working directory.<\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n
<\/td>\n\n

quit<\/b><\/p>\n<\/td>\n

<\/td>\n\n

Quit debugfs<\/b><\/p>\n<\/td>\n

 <\/td>\n<\/tr>\n<\/table>\n

rdump<\/b> directory[…] destination<\/i><\/p>\n

Recursively dump directory<\/i>, or multiple directories<\/i>, and all its contents (including regular files, symbolic links, and other directories) into the named destination<\/i>, which should be an existing directory on the native filesystem.<\/p>\n

rm<\/b> pathname<\/i><\/p>\n

Unlink pathname<\/i>. If this causes the inode pointed to by pathname<\/i> to have no other references, deallocate the file. This command functions as the unlink() system call.<\/p>\n

rmdir<\/b> filespec<\/i><\/p>\n

Remove the directory filespec<\/i>.<\/p>\n

setb<\/b> block [count]<\/i><\/p>\n

Mark the block number block<\/i> as allocated. If the optional argument count<\/i> is present, then count<\/i> blocks starting at block number block<\/i> will be marked as allocated.<\/p>\n

set_block_group<\/b> bgnum field value<\/i><\/p>\n

Modify the block group descriptor specified by bgnum<\/i> so that the block group descriptor field field<\/i> has value value<\/i>. Also available as set_bg<\/b>.<\/p>\n

set_current_time<\/b> time<\/i><\/p>\n

Set current time in seconds since Unix epoch to use when setting filesystem fields.<\/p>\n

seti<\/b> filespec [num]<\/i><\/p>\n

Mark inode filespec<\/i> as in use in the inode bitmap. If num<\/i> is specified, also set num-1 inodes after the specified inode.<\/p>\n

set_inode_field<\/b> filespec field value<\/i><\/p>\n

Modify the inode specified by filespec<\/i> so that the inode field field<\/i> has value value.<\/i> The list of valid inode fields which can be set via this command can be displayed by using the command: set_inode_field -l<\/b> Also available as sif<\/b>.<\/p>\n

set_mmp_value<\/b> field value<\/i><\/p>\n

Modify the multiple-mount protection (MMP) data so that the MMP field field<\/i> has value value.<\/i> The list of valid MMP fields which can be set via this command can be displayed by using the command: set_mmp_value -l<\/b> Also available as smmp<\/b>.<\/p>\n

set_super_value<\/b> field value<\/i><\/p>\n

Set the superblock field field<\/i> to value.<\/i> The list of valid superblock fields which can be set via this command can be displayed by using the command: set_super_value -l<\/b> Also available as ssv<\/b>.<\/p>\n

show_debugfs_params<\/b><\/p>\n

Display debugfs<\/b> parameters such as information about currently opened filesystem.<\/p>\n

show_super_stats<\/b> [-h]<\/i><\/p>\n

List the contents of the super block and the block group descriptors. If the -h<\/i> flag is given, only print out the superblock contents. Also available as stats<\/b>.<\/p>\n

stat<\/b> filespec<\/i><\/p>\n

Display the contents of the inode structure of the inode filespec<\/i>.<\/p>\n

supported_features<\/b><\/p>\n

Display filesystem features supported by this version of debugfs<\/b>.<\/p>\n

testb<\/b> block [count]<\/i><\/p>\n

Test if the block number block<\/i> is marked as allocated in the block bitmap. If the optional argument count<\/i> is present, then count<\/i> blocks starting at block number block<\/i> will be tested.<\/p>\n

testi<\/b> filespec<\/i><\/p>\n

Test if the inode filespec<\/i> is marked as allocated in the inode bitmap.<\/p>\n

undel<\/b> [pathname]<\/i><\/p>\n

Undelete the specified inode number (which must be surrounded by angle brackets) so that it and its blocks are marked in use, and optionally link the recovered inode to the specified pathname. The e2fsck<\/b> command should always be run after using the undel<\/b> command to recover deleted files.<\/p>\n

Note that if you are recovering a large number of deleted files, linking the inode to a directory may require the directory to be expanded, which could allocate a block that had been used by one of the yet-to-be-undeleted files. So it is safer to undelete all of the inodes without specifying a destination pathname, and then in a separate pass, use the debugfs link<\/b> command to link the inode to the destination pathname, or use e2fsck<\/b> to check the filesystem and link all of the recovered inodes to the lost+found directory.<\/p>\n

unlink<\/b> pathname<\/i><\/p>\n

Remove the link specified by pathname<\/i> to an inode. Note this does not adjust the inode reference counts.<\/p>\n

write<\/b> source_file out_file<\/i><\/p>\n

Copy the contents of source_file<\/i> into a newly-created file in the filesystem named out_file<\/i>.<\/p>\n

zap_block<\/b> [-f filespec] [-o offset] [-l length] [-p pattern] block_num<\/i><\/p>\n

Overwrite the block specified by block_num<\/i> with zero (NUL) bytes, or if -p<\/i> is given use the byte specified by pattern<\/i>. If -f<\/i> is given then block_num<\/i> is relative to the start of the file given by filespec<\/i>. The -o<\/i> and -l<\/i> options limit the range of bytes to zap to the specified offset<\/i> and length<\/i> relative to the start of the block.<\/p>\n

zap_block<\/b> [-f filespec] [-b bit] block_num<\/i><\/p>\n

Bit-flip portions of the physical block_num<\/i>. If -f<\/i> is given, then block_num<\/i> is a logical block relative to the start of filespec<\/i>.<\/p>\n

ENVIRONMENT VARIABLES <\/a> <\/h2>\n

DEBUGFS_PAGER, PAGER<\/b><\/p>\n

The debugfs<\/b> program always pipes the output of the some commands through a pager program. These commands include: show_super_stats<\/i> (stats<\/i>), list_directory<\/i> (ls<\/i>), show_inode_info<\/i> (stat<\/i>), list_deleted_inodes<\/i> (lsdel<\/i>), and htree_dump<\/i>. The specific pager can explicitly specified by the DEBUGFS_PAGER<\/b> environment variable, and if it is not set, by the PAGER<\/b> environment variable.<\/p>\n

Note that since a pager is always used, the less<\/b>(1) pager is not particularly appropriate, since it clears the screen before displaying the output of the command and clears the output the screen when the pager is exited. Many users prefer to use the less<\/b>(1) pager for most purposes, which is why the DEBUGFS_PAGER<\/b> environment variable is available to override the more general PAGER<\/b> environment variable.<\/p>\n

AUTHOR <\/a> <\/h2>\n

debugfs<\/b> was written by Theodore Ts\u2019o .<\/p>\n

SEE ALSO <\/a> <\/h2>\n

dumpe2fs<\/b>(8), tune2fs<\/b>(8), e2fsck<\/b>(8), mke2fs<\/b>(8), ext4<\/b>(5)<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

debugfs \u2212 ext2\/ext3\/ext4 file system debugger <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,196,4],"class_list":["post-3127","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-debugfs","tag-man8"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3127","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3127"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3127\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3127"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3127"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3127"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}