Date: Fri, 25 Oct 2013 17:11:17 -0500 From: Larry Rosenman <ler@lerctr.org> To: J David <j.david.lists@gmail.com> Cc: Freebsd fs <freebsd-fs@freebsd.org>, current@freebsd.org, jdavidlists@gmail.com Subject: Re: ZFS: Invalid SEND/RECV stream still Message-ID: <723e41d2533cfb09bf6892a172592744@webmail.lerctr.org> In-Reply-To: <CABXB=RSmhdQrT9JFtQK_kqcJP-DBE4%2Bc0%2Bs%2BM-0RifBFEomnxQ@mail.gmail.com> References: <c0a42b456769e22f908e689a1de56c82@webmail.lerctr.org> <201310251933.r9PJX8sx086597@hergotha.csail.mit.edu> <29a687d287cf28d34283566eba509486@webmail.lerctr.org> <CABXB=RSmhdQrT9JFtQK_kqcJP-DBE4%2Bc0%2Bs%2BM-0RifBFEomnxQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-10-25 17:09, J David wrote: > On Fri, Oct 25, 2013 at 3:36 PM, Larry Rosenman <ler@lerctr.org> wrote: >>>> cannot receive incremental stream: invalid backup stream > > It may help to decouple the steps. I.e. do a "zfs send blah blah >> file" then copy the file and do a "zfs recv blah blah <file" on the > second host. > > If nothing else, it should help you demonstrate that it's not the > machine-to-machine copy that's at fault, because you can take the > sha256 sum of the file on both sides and prove it's the same. > > Good luck! we've tried this, and still the same issue. So. I'm not sure how to diagnose it. The message out of zfs send/recv is not very informative. Other ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: ler@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?723e41d2533cfb09bf6892a172592744>