-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
-h Display a usage message.
-n Dry-run; do not actually write blocks back to the filesystem.
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 environment variable.
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
email@example.com. This page was obtained from the project's
upstream Git repository
⟨git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git⟩ on 2020-08-13.
(At that time, the date of the most recent commit that was found in
the repository was 2020-03-21.) If you discover any rendering prob‐
lems in this HTML version of the page, or you believe there is a bet‐
ter 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 firstname.lastname@example.org
E2fsprogs version 1.46-WIP March 2020 E2UNDO(8)