]> git.ipfire.org Git - thirdparty/e2fsprogs.git/blame_incremental - debugfs/debugfs.8.in
Add ext4 man page and update and clean up the other man pages
[thirdparty/e2fsprogs.git] / debugfs / debugfs.8.in
... / ...
CommitLineData
1.\" -*- nroff -*-
2.\" Copyright 1993, 1994, 1995 by Theodore Ts'o. All Rights Reserved.
3.\" This file may be copied under the terms of the GNU Public License.
4.\"
5.TH DEBUGFS 8 "@E2FSPROGS_MONTH@ @E2FSPROGS_YEAR@" "E2fsprogs version @E2FSPROGS_VERSION@"
6.SH NAME
7debugfs \- ext2/ext3/ext4 file system debugger
8.SH SYNOPSIS
9.B debugfs
10[
11.B \-DVwci
12]
13[
14.B \-b
15blocksize
16]
17[
18.B \-s
19superblock
20]
21[
22.B \-f
23cmd_file
24]
25[
26.B \-R
27request
28]
29[
30.B \-d
31data_source_device
32]
33[
34device
35]
36.SH DESCRIPTION
37The
38.B debugfs
39program is an interactive file system debugger. It can be used to
40examine and change the state of an ext2, ext3, or ext4 file system.
41.br
42.I device
43is the special file corresponding to the device containing the
44file system (e.g /dev/hdXX).
45.SH OPTIONS
46.TP
47.I \-w
48Specifies that the file system should be opened in read-write mode.
49Without this option, the file system is opened in read-only mode.
50.TP
51.I \-c
52Specifies that the file system should be opened in catastrophic mode, in
53which the inode and group bitmaps are not read initially. This can be
54useful for filesystems with significant corruption, but because of this,
55catastrophic mode forces the filesystem to be opened read-only.
56.TP
57.I \-i
58Specifies that
59.I device
60represents an ext2 image file created by the
61.B e2image
62program. Since the ext2 image file only contains the superblock, block
63group descriptor, block and inode allocation bitmaps, and
64the inode table, many
65.B debugfs
66commands will not function properly.
67.B Warning:
68no safety checks are in place, and
69.B debugfs
70may fail in interesting ways if commands such as
71.IR ls ", " dump ", "
72etc. are tried without specifying the
73.I data_source_device
74using the
75.I \-d
76option.
77.B debugfs
78is a debugging tool. It has rough edges!
79.TP
80.I -d data_source_device
81Used with the
82.I \-i
83option, specifies that
84.I data_source_device
85should be used when reading blocks not found in the ext2 image file.
86This includes data, directory, and indirect blocks.
87.TP
88.I -b blocksize
89Forces the use of the given block size for the file system, rather than
90detecting the correct block size as normal.
91.TP
92.I -s superblock
93Causes the file system superblock to be read from the given block
94number, instead of using the primary superblock (located at an offset of
951024 bytes from the beginning of the filesystem). If you specify the
96.I -s
97option, you must also provide the blocksize of the filesystem via the
98.I -b
99option.
100.TP
101.I -f cmd_file
102Causes
103.B debugfs
104to read in commands from
105.IR cmd_file ,
106and execute them. When
107.B debugfs
108is finished executing those commands, it will exit.
109.TP
110.I -D
111Causes
112.B debugfs
113to open the device using Direct I/O, bypassing the buffer cache. Note
114that some Linux devices, notably device mapper as of this writing, do
115not support Direct I/O.
116.TP
117.I -R request
118Causes
119.B debugfs
120to execute the single command
121.IR request ,
122and then exit.
123.TP
124.I -V
125print the version number of
126.B debugfs
127and exit.
128.SH SPECIFYING FILES
129Many
130.B debugfs
131commands take a
132.I filespec
133as an argument to specify an inode (as opposed to a pathname)
134in the filesystem which is currently opened by
135.BR debugfs .
136The
137.I filespec
138argument may be specified in two forms. The first form is an inode
139number surrounded by angle brackets, e.g.,
140.IR <2> .
141The 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
143which is currently opened by
144.BR debugfs .
145If not, the pathname is
146interpreted relative to the current working directory as maintained by
147.BR debugfs .
148This may be modified by using the
149.B debugfs
150command
151.IR cd .
152.\"
153.\"
154.\"
155.SH COMMANDS
156This is a list of the commands which
157.B debugfs
158supports.
159.TP
160.BI blocks " filespace"
161Print the blocks used by the inode
162.I filespec
163to stdout.
164.TP
165.BI bmap " filespec logical_block"
166Print the physical block number corresponding to the logical block number
167.I logical_block
168in the inode
169.IR filespec .
170.TP
171.BI block_dump " [-f filespec] block_num"
172Dump the filesystem block given by
173.I block_num
174in hex and ASCII format to the console. If the
175.I -f
176option is specified, the block number is relative to the start of the given
177.BR filespec .
178.TP
179.BI cat " filespec"
180Dump the contents of the inode
181.I filespec
182to stdout.
183.TP
184.BI cd " filespec"
185Change the current working directory to
186.IR filespec .
187.TP
188.BI chroot " filespec"
189Change the root directory to be the directory
190.IR filespec .
191.TP
192.BI close " [-a]"
193Close the currently open file system. If the
194.I -a
195option is specified, write out any changes to the superblock and block
196group descriptors to all of the backup superblocks, not just to the
197master superblock.
198.TP
199.BI clri " filespec"
200Clear the contents of the inode
201.IR filespec .
202.TP
203.BI dirsearch " filespec filename"
204Search the directory
205.I filespec
206for
207.IR filename .
208.TP
209.B dirty
210Mark the filesystem as dirty, so that the superblocks will be written on exit.
211.TP
212.BI dump " [-p] filespec out_file"
213Dump the contents of the inode
214.I filespec
215to the output file
216.IR out_file .
217If the
218.I -p
219option is given set the owner, group and permissions information on
220.I out_file
221to match
222.IR filespec .
223.TP
224.B dump_mmp
225Display the multiple-mount protection (mmp) field values.
226.TP
227.BI dx_hash " [-h hash_alg] [-s hash_seed] filename"
228Calculate the directory hash of
229.IR filename .
230The hash algorithm specified with
231.I -h
232may be
233.BR legacy , " half_md4" ", or " tea .
234The hash seed specified with
235.I -s
236must be in UUID format.
237.TP
238.BI dump_extents " [-n] [-l] filespec"
239Dump the the extent tree of the inode
240.IR filespec .
241The
242.I -n
243flag will cause
244.B dump_extents
245to only display the interior nodes in the extent tree. The
246.I -l
247flag will cause
248.B dump_extents
249to only display the leaf nodes in the extent tree.
250.IP
251(Please note that the length and range of blocks for the last extent in
252an interior node is an estimate by the extents library functions, and is
253not stored in filesystem data structures. Hence, the values displayed
254may not necessarily by accurate and does not indicate a problem or
255corruption in the file system.)
256.TP
257.BI expand_dir " filespec"
258Expand the directory
259.IR filespec .
260.TP
261.BI feature " [fs_feature] [-fs_feature] ..."
262Set or clear various filesystem features in the superblock. After setting
263or clearing any filesystem features that were requested, print the current
264state of the filesystem feature set.
265.TP
266.BI filefrag " [-dvr] filespec"
267Print the number of contiguous extents in
268.IR filespec .
269If
270.I filespec
271is a directory and the
272.I -d
273option is not specified,
274.I filefrag
275will print the number of contiguous extents for each file in
276the directory. The
277.I -v
278option will cause
279.I filefrag
280print a tabular listing of the contiguous extents in the
281file. The
282.I -r
283option will cause
284.I filefrag
285to do a recursive listing of the directory.
286.TP
287.BI find_free_block " [count [goal]]"
288Find the first
289.I count
290free blocks, starting from
291.I goal
292and allocate it. Also available as
293.BR ffb .
294.TP
295.BI find_free_inode " [dir [mode]]"
296Find a free inode and allocate it. If present,
297.I dir
298specifies the inode number of the directory
299which the inode is to be located. The second
300optional argument
301.I mode
302specifies the permissions of the new inode. (If the directory bit is set
303on the mode, the allocation routine will function differently.) Also
304available as
305.BR ffi .
306.TP
307.BI freeb " block [count]"
308Mark the block number
309.I block
310as not allocated.
311If the optional argument
312.I count
313is present, then
314.I count
315blocks starting at block number
316.I block
317will be marked as not allocated.
318.TP
319.BI freefrag " [-c chunk_kb]"
320Report free space fragmentation on the currently open file system.
321If the
322.I \-c
323option is specified then the filefrag command will print how many free
324chunks of size
325.I chunk_kb
326can be found in the file system. The chunk size must be a power of two
327and be larger than the file system block size.
328.TP
329.BI freei " filespec [num]"
330Free the inode specified by
331.IR filespec .
332If
333.I num
334is specified, also clear num-1 inodes after the specified inode.
335.TP
336.B help
337Print a list of commands understood by
338.BR debugfs .
339.TP
340.BI htree_dump " filespec"
341Dump the hash-indexed directory
342.IR filespec ,
343showing its tree structure.
344.TP
345.BI icheck " block ..."
346Print a listing of the inodes which use the one or more blocks specified
347on the command line.
348.TP
349.BI imap " filespec"
350Print the location of the inode data structure (in the inode table)
351of the inode
352.IR filespec .
353.TP
354.BI init_filesys " device blocksize"
355Create an ext2 file system on
356.I device
357with device size
358.IR blocksize .
359Note that this does not fully initialize all of the data structures;
360to do this, use the
361.BR mke2fs (8)
362program. This is just a call to the low-level library, which sets up
363the superblock and block descriptors.
364.TP
365.BI kill_file " filespec"
366Deallocate the inode
367.I filespec
368and its blocks. Note that this does not remove any directory
369entries (if any) to this inode. See the
370.BR rm (1)
371command if you wish to unlink a file.
372.TP
373.BI lcd " directory"
374Change the current working directory of the
375.B debugfs
376process to
377.I directory
378on the native filesystem.
379.TP
380.BI ln " filespec dest_file"
381Create a link named
382.I dest_file
383which is a hard link to
384.IR filespec .
385Note this does not adjust the inode reference counts.
386.TP
387.BI logdump " [-acs] [-b block] [-i filespec] [-f journal_file] [output_file]"
388Dump the contents of the ext3 journal. By default, dump the journal inode as
389specified in the superblock. However, this can be overridden with the
390.I \-i
391option, which dumps the journal from the internal inode given by
392.IR filespec .
393A regular file containing journal data can be specified using the
394.I \-f
395option. Finally, the
396.I \-s
397option utilizes the backup information in the superblock to locate the
398journal.
399.IP
400The
401.I \-a
402option causes the
403.B logdump
404program to print the contents of all of the descriptor blocks.
405The
406.I \-b
407option causes
408.B logdump
409to print all journal records that are refer to the specified block.
410The
411.I \-c
412option will print out the contents of all of the data blocks selected by
413the
414.I \-a
415and
416.I \-b
417options.
418.TP
419.BI ls " [-d] [-l] [-p] filespec"
420Print a listing of the files in the directory
421.IR filespec .
422The
423.I \-d
424flag will list deleted entries in the directory.
425The
426.I \-l
427flag will list files using a more verbose format.
428The
429.I \-p
430flag will list the files in a format which is more easily parsable by
431scripts, as well as making it more clear when there are spaces or other
432non-printing characters at the end of filenames.
433.TP
434.BI modify_inode " filespec"
435Modify the contents of the inode structure in the inode
436.IR filespec .
437Also available as
438.BR mi .
439.TP
440.BI mkdir " filespec"
441Make a directory.
442.TP
443.BI mknod " filespec [p|[[c|b] major minor]]"
444Create a special device file (a named pipe, character or block device).
445If a character or block device is to be made, the
446.I major
447and
448.I minor
449device numbers must be specified.
450.TP
451.BI ncheck " [-c] inode_num ..."
452Take the requested list of inode numbers, and print a listing of pathnames
453to those inodes. The
454.I -c
455flag will enable checking the file type information in the directory
456entry to make sure it matches the inode's type.
457.TP
458.BI open " [-weficD] [-b blocksize] [-s superblock] device"
459Open a filesystem for editing. The
460.I -f
461flag forces the filesystem to be opened even if there are some unknown
462or incompatible filesystem features which would normally
463prevent the filesystem from being opened. The
464.I -e
465flag causes the filesystem to be opened in exclusive mode. The
466.IR -b ", " -c ", " -i ", " -s ", " -w ", and " -D
467options behave the same as the command-line options to
468.BR debugfs .
469.TP
470.BI punch " filespec start_blk [end_blk]"
471Delete the blocks in the inode ranging from
472.I start_blk
473to
474.IR end_blk .
475If
476.I end_blk
477is omitted then this command will function as a truncate command; that
478is, all of the blocks starting at
479.I start_blk
480through to the end of the file will be deallocated.
481.TP
482.I symlink filespec target
483Make a symbolic link.
484.TP
485.B pwd
486Print the current working directory.
487.TP
488.B quit
489Quit
490.B debugfs
491.TP
492.BI rdump " directory destination"
493Recursively dump
494.I directory
495and all its contents (including regular files, symbolic links, and other
496directories) into the named
497.I destination
498which should be an existing directory on the native filesystem.
499.TP
500.BI rm " pathname"
501Unlink
502.IR pathname .
503If this causes the inode pointed to by
504.I pathname
505to have no other references, deallocate the file. This command functions
506as the unlink() system call.
507.I
508.TP
509.BI rmdir " filespec"
510Remove the directory
511.IR filespec .
512.TP
513.BI setb " block [count]"
514Mark the block number
515.I block
516as allocated.
517If the optional argument
518.I count
519is present, then
520.I count
521blocks starting at block number
522.I block
523will be marked as allocated.
524.TP
525.BI set_block_group " bgnum field value"
526Modify the block group descriptor specified by
527.I bgnum
528so that the block group descriptor field
529.I field
530has value
531.IR value .
532Also available as
533.BR set_bg .
534.TP
535.BI seti " filespec [num]"
536Mark inode
537.I filespec
538as in use in the inode bitmap. If
539.I num
540is specified, also set num-1 inodes after the specified inode.
541.TP
542.BI set_inode_field " filespec field value"
543Modify the inode specified by
544.I filespec
545so that the inode field
546.I field
547has value
548.I value.
549The list of valid inode fields which can be set via this command
550can be displayed by using the command:
551.B set_inode_field -l
552Also available as
553.BR sif .
554.TP
555.BI set_mmp_value " field value"
556Modify the multiple-mount protection (MMP) data so that the MMP field
557.I field
558has value
559.I value.
560The list of valid MMP fields which can be set via this command
561can be displayed by using the command:
562.B set_mmp_value -l
563Also available as
564.BR smmp .
565.TP
566.BI set_super_value " field value"
567Set the superblock field
568.I field
569to
570.I value.
571The list of valid superblock fields which can be set via this command
572can be displayed by using the command:
573.B set_super_value -l
574Also available as
575.BR ssv .
576.TP
577.BI show_super_stats " [-h]"
578List the contents of the super block and the block group descriptors. If the
579.I -h
580flag is given, only print out the superblock contents. Also available as
581.BR stats .
582.TP
583.BI stat " filespec"
584Display the contents of the inode structure of the inode
585.IR filespec .
586.TP
587.BI testb " block [count]"
588Test if the block number
589.I block
590is marked as allocated in the block bitmap.
591If the optional argument
592.I count
593is present, then
594.I count
595blocks starting at block number
596.I block
597will be tested.
598.TP
599.BI testi " filespec"
600Test if the inode
601.I filespec
602is marked as allocated in the inode bitmap.
603.TP
604.BI undel " <inode_number> [pathname]"
605Undelete the specified inode number (which must be surrounded by angle
606brackets) so that it and its blocks are marked in use, and optionally
607link the recovered inode to the specified pathname. The
608.B e2fsck
609command should always be run after using the
610.B undel
611command to recover deleted files.
612.IP
613Note that if you are recovering a large number of deleted files, linking
614the inode to a directory may require the directory to be expanded, which
615could allocate a block that had been used by one of the
616yet-to-be-undeleted files. So it is safer to undelete all of the
617inodes without specifying a destination pathname, and then in a separate
618pass, use the debugfs
619.B link
620command to link the inode to the destination pathname, or use
621.B e2fsck
622to check the filesystem and link all of the recovered inodes to the
623lost+found directory.
624.TP
625.BI unlink " pathname"
626Remove the link specified by
627.I pathname
628to an inode. Note this does not adjust the inode reference counts.
629.TP
630.BI write " source_file out_file"
631Copy the contents of
632.I source_file
633into a newly-created file in the filesystem named
634.IR out_file .
635.TP
636.BI zap_block " [-f filespec] [-o offset] [-l length] [-p pattern] block_num"
637.TP
638Overwrite the block specified by
639.I block_num
640with zero (NUL) bytes, or if
641.I -p
642is given use the byte specified by
643.IR pattern .
644If
645.I -f
646is given then
647.I block_num
648is relative to the start of the file given by
649.IR filespec .
650The
651.I -o
652and
653.I -l
654options limit the range of bytes to zap to the specified
655.I offset
656and
657.I length
658relative to the start of the block.
659.TP
660.BI zap_block " [-f filespec] [-b bit] block_num"
661Bit-flip portions of the physical
662.IR block_num .
663If
664.I -f
665is given, then
666.I block_num
667is a logical block relative to the start of
668.IR filespec .
669.SH ENVIRONMENT VARIABLES
670.TP
671.B DEBUGFS_PAGER, PAGER
672The
673.B debugfs
674program always pipes the output of the some commands through a
675pager program. These commands include:
676.IR show_super_stats " (" stats ),
677.IR list_directory " (" ls ),
678.IR show_inode_info " (" stat ),
679.IR list_deleted_inodes " (" lsdel ),
680and
681.IR htree_dump .
682The specific pager can explicitly specified by the
683.B DEBUGFS_PAGER
684environment variable, and if it is not set, by the
685.B PAGER
686environment variable.
687.IP
688Note that since a pager is always used, the
689.BR less (1)
690pager is not particularly appropriate, since it clears the screen before
691displaying the output of the command and clears the output the screen
692when the pager is exited. Many users prefer to use the
693.BR less (1)
694pager for most purposes, which is why the
695.B DEBUGFS_PAGER
696environment variable is available to override the more general
697.B PAGER
698environment variable.
699.SH AUTHOR
700.B debugfs
701was written by Theodore Ts'o <tytso@mit.edu>.
702.SH SEE ALSO
703.BR dumpe2fs (8),
704.BR tune2fs (8),
705.BR e2fsck (8),
706.BR mke2fs (8),
707.BR ext4 (5)