Package: e2fsprogs Version: 1.41.12-4stable1 Severity: minor Tags: patch From "man ..." ("groff -ww ..."):
<groff: e2image.8>:116: warning: escape character ignored before a tab character Some spaces adjusted, removed Period (full stop) in abbreviations protected. Patch: --- e2image.8 2012-05-23 01:59:35.000000000 +0000 +++ e2image.8.new 2012-05-23 02:07:41.000000000 +0000 @@ -15,11 +15,11 @@ .SH DESCRIPTION The .B e2image -program will save critical ext2, ext3, or ext4 filesystem metadata located on -.I device -to a file specified by +program will save critical ext2, ext3, or ext4 filesystem metadata located on +.I device +to a file specified by .IR image-file . -The image file may be examined by +The image file may be examined by .B dumpe2fs and .BR debugfs , @@ -30,15 +30,15 @@ e2fsck will be enhanced to be able to use the image file to help recover a badly damaged filesystem. .PP -If +If .I image-file -is \-, then the output of +is \-, then the output of .B e2image will be sent to standard output, so that the output can be piped to -another program, such as -.BR gzip (1). +another program, such as +.BR gzip (1). (Note that this is currently only supported when -creating a raw image file using the +creating a raw image file using the .B \-r option, since the process of creating a normal image file currently requires random access to the file, which cannot be done using a @@ -47,22 +47,22 @@ .PP It is a very good idea to create image files for all of filesystems on a system and save the partition -layout (which can be generated using the +layout (which can be generated using the .B fdisk \-l command) at regular intervals --- at boot time, and/or every week or so. The image file should be stored on some filesystem other than the filesystem whose data it contains, to ensure that this data is accessible in the case where the filesystem has been badly damaged. .PP -To save disk space, +To save disk space, .B e2image -creates the image file as a sparse file. +creates the image file as a sparse file. Hence, if the image file needs to be copied to another location, it should -either be compressed first or copied using the +either be compressed first or copied using the .B \-\-sparse=always -option to the GNU version of -.BR cp . +option to the GNU version of +.BR cp . .PP The size of an ext2 image file depends primarily on the size of the filesystems and how many inodes are in use. For a typical 10 gigabyte @@ -75,15 +75,15 @@ .PP .SH RESTORING FILESYSTEM METADATA USING AN IMAGE FILE .PP -The -.B \-I +The +.B \-I option will cause e2image to install the metadata stored in the image -file back to the device. It can be used to restore the filesystem metadata +file back to the device. It can be used to restore the filesystem metadata back to the device in emergency situations. .PP .B WARNING!!!! The -.B \-I +.B \-I option should only be used as a desperation measure when other alternatives have failed. If the filesystem has changed since the image file was created, data @@ -93,13 +93,13 @@ strategies afterwards. .PP .SH RAW IMAGE FILES -The +The .B \-r -option will create a raw image file instead of a normal image file. +option will create a raw image file instead of a normal image file. A raw image file differs from a normal image file in two ways. First, the filesystem metadata is placed in the proper position so that e2fsck, dumpe2fs, debugfs, -etc. can be run directly on the raw image file. In order to minimize +etc.\& can be run directly on the raw image file. In order to minimize the amount of disk space consumed by a raw image file, the file is created as a sparse file. (Beware of copying or compressing/decompressing this file with utilities that don't understand @@ -113,30 +113,29 @@ recommended command is as follows (replace hda1 with the appropriate device): .PP .br -\ \fBe2image \-r /dev/hda1 \- | bzip2 > hda1.e2i.bz2\fR + \fBe2image \-r /dev/hda1 \- | bzip2 > hda1.e2i.bz2\fR .PP -This will only send the metadata information, without any data blocks. +This will only send the metadata information, without any data blocks. However, the filenames in the directory blocks can still reveal information about the contents of the filesystem that the bug reporter may wish to keep confidential. To address this concern, the .B \-s option can be specified. This will cause -.B e2image +.B e2image to scramble directory entries and zero out any unused portions of the directory blocks before writing the image file. However, -the +the .B \-s option will prevent analysis of problems related to hash-tree indexed directories. .PP .SH AUTHOR -.B e2image +.B e2image was written by Theodore Ts'o (ty...@mit.edu). .SH AVAILABILITY .B e2image -is part of the e2fsprogs package and is available from +is part of the e2fsprogs package and is available from http://e2fsprogs.sourceforge.net. .SH SEE ALSO .BR dumpe2fs (8), .BR debugfs (8) - -- System Information: Debian Release: 6.0.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i586) Kernel: Linux 2.6.32-45 Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Versions of packages e2fsprogs depends on: ii e2fslibs 1.41.12-4stable1 ext2/ext3/ext4 file system librari ii libblkid1 2.17.2-9 block device id library ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcomerr2 1.41.12-4stable1 common error description library ii libss2 1.41.12-4stable1 command-line interface parsing lib ii libuuid1 2.17.2-9 Universally Unique ID library ii util-linux 2.17.2-9 Miscellaneous system utilities e2fsprogs recommends no packages. Versions of packages e2fsprogs suggests: pn e2fsck-static <none> (no description available) pn gpart <none> (no description available) pn parted <none> (no description available) -- no debconf information -- Bjarni I. Gislason -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org