-$Id: CHANGES,v 1.307 2010/03/08 10:40:52 stelian Exp $
+$Id: CHANGES,v 1.308 2010/03/08 10:57:24 stelian Exp $
Changes between versions 0.4b42 and 0.4b43 (released ?????????????)
===================================================================
extracted in 'restore -N' mode. Thanks to Jan Görig
<jgorig@users.sourceforge.net> for the patch.
+6. Make the dump man page explicit about ext4 support.
+
Changes between versions 0.4b41 and 0.4b42 (released June 18, 2009)
===================================================================
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $Id: dump.8.in,v 1.62 2009/06/18 09:40:03 stelian Exp $
+.\" $Id: dump.8.in,v 1.63 2010/03/08 10:57:24 stelian Exp $
.\"
.TH DUMP 8 "version __VERSION__ of __DATE__" BSD "System management commands"
.SH NAME
-dump \- ext2/3 filesystem backup
+dump \- ext2/3/4 filesystem backup
.SH SYNOPSIS
.B dump
[\fB\-\fIlevel#\fR]
[\fB\-W \fR| \fB\-w\fR]
.SH DESCRIPTION
.B Dump
-examines files on an ext2/3 filesystem and determines which files need to be
+examines files on an ext2/3/4 filesystem and determines which files need to be
backed up. These files are copied to the given disk, tape or other storage
medium for safe keeping (see the
.B \-f
.B dump
writes in sequence to
.I <prefix>001, <prefix>002
-etc. This can be useful when dumping to files on an ext2 partition, in order to
+etc. This can be useful when dumping to files on an ext2/3/4 partition, in order to
bypass the 2GB file size limitation.
.TP
.BI \-n
exits with zero status on success. Startup errors are indicated with an exit
code of 1; abnormal termination is indicated with an exit code of 3.
.SH BUGS
-It might be considered a bug that this version of dump can only handle ext2/3
+It might be considered a bug that this version of dump can only handle ext2/3/4
filesystems. Specifically, it does not work with FAT filesystems.
.PP
Fewer than 32 read errors (change this with
When a read error occurs,
.B dump
prints out the corresponding physical disk block and sector number and the
-ext2/3 logical block number. It doesn't print out the corresponding file name or
+ext2/3/4 logical block number. It doesn't print out the corresponding file name or
even the inode number. The user has to use
.BR debugfs (8),
commands