#
PKG_MAJOR=2
PKG_MINOR=6
-PKG_REVISION=18
+PKG_REVISION=19
PKG_BUILD=1
+xfsprogs (2.6.19-1) unstable; urgency=low
+
+ * New upstream release.
+
+ -- Nathan Scott <nathans@debian.org> Sat, 17 Jul 2004 11:28:39 +1000
+
xfsprogs (2.6.18-1) unstable; urgency=low
* New upstream release.
+xfsprogs-2.6.19 (16 July 2004)
+ - Fix two byte count size wraps in xfs_copy.
+ - Minor man page fixes from Eric Raymond.
+
xfsprogs-2.6.18 (23 June 2004)
- Fix libhandle from possibly returning an invalid
handle length on systems where size_t is 64 bits.
in the file that do not have any corresponding blocks (\f2hole\f1s).
Each line of the listings takes the following form:
-.Ex
-\f2extent\f1\f7: [\f1\f2startoffset\f1\f7..\f1\f2endoffset\f1\f7]: \c
+.nf
+.ft CW
+ \f2extent\f1\f7: [\f1\f2startoffset\f1\f7..\f1\f2endoffset\f1\f7]: \c
\f1\f2startblock\f1\f7..\f1\f2endblock\f1
-.Ee
+.ft
+.fi
Holes are marked by replacing the \f2startblock..endblock\f1 with \f2hole\fP.
All the file offsets and disk blocks are in units of 512-byte blocks,
.PP
If the \f3-l\f1 option is used, then
-.Ex
-\f1\f2<nblocks>\f1\f7 \f1\f2blocks\f1\f7
-.Ee
+.nf
+.ft CW
+ \f1\f2<nblocks>\f1\f7 \f1\f2blocks\f1\f7
+.ft
+.fi
will be appended to each line. \f1\f2Nblocks\f1\f7 is the length
of the extent described on the line in units of 512-byte blocks.
rather than produce useful output.
If the filesystem is completely corrupt, a core dump might
be produced instead of the message
-.Ex
-\f2xxx\f1\f7 is not a valid filesystem\f1
-.Ee
+.nf
+.ft CW
+ \f2xxx\f1\f7 is not a valid filesystem\f1
+.ft
+.fi
.PP
If the filesystem is very large (has many files) then
.I xfs_check
might run out of memory.
In this case the message
-.Ex
-out of memory
-.Ee
+.nf
+.ft CW
+ out of memory
+.ft
+.fi
is printed.
.PP
The following is a description of the most likely problems and the associated