Hey Richard,
I've just seen that somebody else has been caught out by this. Do you think it
would be worth adding an RFE to add 'send to file' support to ZFS send?
I'll be using data piped to file myself, and while I'm not worried about
corruption myself, if ZFS send knows it's sending to a
Ross wrote:
Hey Richard,
I've just seen that somebody else has been caught out by this. Do you think
it would be worth adding an RFE to add 'send to file' support to ZFS send?
No. Pipes are a foundation of UNIX and are much more flexible
than a fixed file interface (as shown below...
Hi Richard,
Thanks for the detailed reply, and the work behind the scenes filing the CRs.
I've bookmarked both, and will keep a keen eye on them for status changes.
As Miles put it, I'll have to put these dumps into storage for possible future
use.
I do dearly hope that I'll be able to recover
Hi Mattias Miles.
To test the version mismatch theory, I setup a snv_91 VM (using virtualbox) on
my snv_95 desktop, and tried the zfs receive again. Unfortunately the symptoms
are exactly the same: around the ~20GB mark, the justhome.zfs stream still
bombs out with the checksum error.
I
2008/8/13 Jonathan Wheeler [EMAIL PROTECTED]:
So far we've established that in this case:
*Version mismatches aren't causing the problem.
*Receiving across the network isn't the issue (because I have the exact same
issue restoring the stream directly on
my file server).
*All that's left was
Mattias Pantzare wrote:
2008/8/13 Jonathan Wheeler [EMAIL PROTECTED]:
So far we've established that in this case:
*Version mismatches aren't causing the problem.
*Receiving across the network isn't the issue (because I have the exact same
issue restoring the stream directly on
my file
jw == Jonathan Wheeler [EMAIL PROTECTED] writes:
mp == Mattias Pantzare [EMAIL PROTECTED] writes:
jw Miles: zfs receive -nv works ok
one might argue 'zfs receive' should validate checksums with the -n
option, so you can check if a just-written dump is clean before
counting on it. Without
Thanks for the information, I'm learning quite a lot from all this.
It seems to me that zfs send *should* be doing some kind of verification, since
some work has clearly been put into zfs so that zfs's can be dumped into
files/pipes. It's a great feature to have, and I can't believe that this
jw == Jonathan Wheeler [EMAIL PROTECTED] writes:
jw A common example used all over the place is zfs send | ssh
jw $host. In these examples is ssh guaranteeing the data delivery
jw somehow?
it is really all just appologetics. It sounds like a zfs bug to me.
The only alternative is
Jonathan Wheeler wrote:
Thanks for the information, I'm learning quite a lot from all this.
It seems to me that zfs send *should* be doing some kind of verification,
since some work has clearly been put into zfs so that zfs's can be dumped
into files/pipes. It's a great feature to have, and
There is an explicit check in ZFS for the checksum, as you deduced. I suspect
that by disabling this check you could recover much, if not all, of your data.
You could probably do this with mdb by 'simply' writing a NOP over the branch
in dmu_recv_stream.
It appears that 'zfs send' was designed
Hi folks,
Perhaps I was a little verbose in my first post, putting a view people off.
Does anyone else have any ideas on this one.
I can't be the first person to have had a problem with a zfs backup stream. Is
there nothing that can be done to recover at least some of the stream.
As another
2008/8/10 Jonathan Wheeler [EMAIL PROTECTED]:
Hi Folks,
I'm in the very unsettling position of fearing that I've lost all of my data
via a zfs send/receive operation, despite ZFS's legendary integrity.
The error that I'm getting on restore is:
receiving full stream of faith/[EMAIL
mp == Mattias Pantzare [EMAIL PROTECTED] writes:
mp Or the file was corrupted when you transfered it.
he stored the backup streams on ZFS, so obviously they couldn't
possibly be corrupt. :p
Jonathan, does 'zfs receive -nv' also detect the checksum error, or is
it only detected when you
Hi Folks,
I'm in the very unsettling position of fearing that I've lost all of my data
via a zfs send/receive operation, despite ZFS's legendary integrity.
The error that I'm getting on restore is:
receiving full stream of faith/[EMAIL PROTECTED] into Z/faith/[EMAIL PROTECTED]
cannot receive:
15 matches
Mail list logo