-f Normally, e2undo will check the filesystem superblock to
make sure the undo log matches with the filesystem on the
device. If they do not match, e2undo will refuse to apply
the undo log as a safety mechanism. The -f option
disables this safety mechanism.
-h Display a usage message.
-n Dry-run; do not actually write blocks back to the
Specify the filesystem's offset (in bytes) from the
beginning of the device or file.
-v Report which block we're currently replaying.
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 e2undo-device.e2undo in
the directory specified via the E2FSPROGS_UNDO_DIR
WARNING: The undo file cannot be used to recover from a
power or system crash.
This page is part of the e2fsprogs (utilities for ext2/3/4
filesystems) project. Information about the project can be found
at ⟨http://e2fsprogs.sourceforge.net/⟩. It is not known how to
report bugs for this man page; if you know, please send a mail to
firstname.lastname@example.org. This page was obtained from the project's
upstream Git repository
2021-04-01. (At that time, the date of the most recent commit
that was found in the repository was 2021-02-28.) If you
discover any rendering problems in this HTML version of the page,
or you believe there is a better or more up-to-date source for
the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original
manual page), send a mail to email@example.com
E2fsprogs version 1.46.2 February 2021 E2UNDO(8)