Adds information regarding image consistency when using e2image on a read-write filesystem and about -f option used now to force the image creation of a read-write filesystem Signed-off-by: Carlos Maiolino <cmaiolino@xxxxxxxxxx> --- misc/e2image.8.in | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/misc/e2image.8.in b/misc/e2image.8.in index 84b9729..eb22f42 100644 --- a/misc/e2image.8.in +++ b/misc/e2image.8.in @@ -30,6 +30,18 @@ recovering catastrophically corrupted filesystems. In the future, e2fsck will be enhanced to be able to use the image file to help recover a badly damaged filesystem. .PP +When getting an image to be used for debugging purposes, is necessary that the +filesystem be unmounted or in a Read-Only state, to ensure the image-file will +be in a consistent state. Although, it's possible to force an image-file +creation using the +.B -f +option. For images saved for metadata backup purposes (to be restored with +.B -I +option), +.B e2image +will be backing up only statically located metadata blocks, so, images taken +from a read-write filesystem are not completely useless, and, although recommended, there is no real need to run it on a Read-Only or unmounted filesystem. +.PP If .I image-file is \-, then the output of -- 1.8.1.4 -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
