Lori Alt wrote:
On 09/04/09 10:17, dick hoogendijk wrote:
Lori Alt wrote:
The -u option to zfs recv (which was just added to support flash
archive installs, but it's useful for other reasons too) suppresses
all mounts of the received file systems. So you can mount them
yourself afterward in
Lori Alt wrote:
The -n option does some verification. It verifies that the record
headers distributed throughout the stream are syntactically valid.
Since each record header contains a length field which allows the next
header to be found, one bad header will cause the processing of the
On 09/04/09 09:41, dick hoogendijk wrote:
Lori Alt wrote:
The -n option does some verification. It verifies that the record
headers distributed throughout the stream are syntactically valid.
Since each record header contains a length field which allows the
next header to be found, one bad
Lori Alt wrote:
The -u option to zfs recv (which was just added to support flash
archive installs, but it's useful for other reasons too) suppresses
all mounts of the received file systems. So you can mount them
yourself afterward in whatever order is appropriate, or do a 'zfs
mount -a'.
You
On 09/04/09 10:17, dick hoogendijk wrote:
Lori Alt wrote:
The -u option to zfs recv (which was just added to support flash
archive installs, but it's useful for other reasons too) suppresses
all mounts of the received file systems. So you can mount them
yourself afterward in whatever order
On Wed, 2 Sep 2009 13:06:35 -0500 (CDT)
Bob Friesenhahn bfrie...@simple.dallas.tx.us wrote:
Nothing prevents validating the self-verifying archive file via this
zfs recv -vn technique.
Does this verify the ZFS format/integrity of the stream?
Or is the only way to do that to zfs recv the stream
On 09/03/09 14:21, dick hoogendijk wrote:
On Wed, 2 Sep 2009 13:06:35 -0500 (CDT)
Bob Friesenhahn bfrie...@simple.dallas.tx.us wrote:
Nothing prevents validating the self-verifying archive file via this
zfs recv -vn technique.
Does this verify the ZFS format/integrity of the stream?
Some time ago there was some discussion on zfs send | rcvd TO A FILE.
Apart form the disadvantages which I now know someone mentioned a CHECK to
be at least sure that the file itself was OK (without one or more bits
that felt over). I lost this reply and would love to hear this check
zfs recv -vn file will check the integrity of the zfs stream in
file. However, this is only a one-time check; if the data is
corrupted later the stream will not be recoverable. You might
consider using something like par2 [1] to generate parity:
while true:
zfs send f...@snap file
generate
On Wed, 2 Sep 2009, Will Murnane wrote:
zfs recv -vn file will check the integrity of the zfs stream in
file. However, this is only a one-time check; if the data is
corrupted later the stream will not be recoverable. You might
consider using something like par2 [1] to generate parity:
The
Dick Hoogendijk wrote:
Some time ago there was some discussion on zfs send | rcvd TO A FILE.
Apart form the disadvantages which I now know someone mentioned a CHECK
to be at least sure that the file itself was OK (without one or more
bits that felt over). I lost this reply and would love to
11 matches
Mail list logo
