Date: Thu, 24 Jul 2014 13:38:20 -0400 From: Allan Jude <allanjude@freebsd.org> To: freebsd-current@freebsd.org Subject: Re: zfs send/recv: STILL invalid Backup Stream Message-ID: <53D1448C.40908@freebsd.org> In-Reply-To: <62315eb454a95db636b7764aad3c0f9b@thebighonker.lerctr.org> References: <62315eb454a95db636b7764aad3c0f9b@thebighonker.lerctr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--onGXlbDDQmSsE6c7p32TBCccxd0ED6Sqx
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 2014-07-24 13:33, Larry Rosenman wrote:
> TRYING to use zfs send/recv between a 10-STABLE and an 11-CURRENT
> system, and receive the non-descript
> "invalid backup stream".
>=20
> borg.lerctr.org /home/ler $ sudo bin/backup-TBH-ZFS-initial.sh
> Password:
> receiving full stream of zroot@2014-07-24 into zroot/backups/TBH@2014-0=
7-24
> received 41.7KB stream in 300 seconds (142B/sec)
> receiving full stream of zroot/usr@2014-07-24 into
> zroot/backups/TBH/usr@2014-07-24
> received 41.7KB stream in 1 seconds (41.7KB/sec)
> receiving full stream of zroot/usr/local@2014-07-24 into
> zroot/backups/TBH/usr/local@2014-07-24
> received 2.81GB stream in 1116 seconds (2.58MB/sec)
> receiving full stream of zroot/usr/src@2014-07-24 into
> zroot/backups/TBH/usr/src@2014-07-24
> cannot receive new filesystem stream: invalid backup stream
> borg.lerctr.org /home/ler $ cat bin/backup-TBH-ZFS-initial.sh
> #!/bin/sh
> DATE=3D`date "+%Y-%m-%d"`
> #DATE2=3D2013-03-24
> #DATE2=3D`date -v "-1d" "+%Y-%m-%d"`
> # snap the source
> ssh root@tbh.lerctr.org zfs snapshot -r zroot@${DATE}
> # zfs copy the source to here.
> ssh root@tbh.lerctr.org "zfs send -R -D zroot@${DATE} | \
> ssh home.lerctr.org \"zfs recv -F -u -v -d zroot/backups/TBH\""
> # make sure we NEVER allow the backup stuff to automount.
> /sbin/zfs list -H -t filesystem -r zroot/backups/TBH| \
> awk '{printf "/sbin/zfs set canmount=3Dnoauto %s\n",$1}' | sh
> borg.lerctr.org /home/ler $
>=20
> This has been happening for YEARS and I can't seem to interest anyone i=
n
> fixing it.
>=20
> How can we get to the bottom of this?
>=20
> borg.lerctr.org /home/ler $ uname -a
> FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #56 r268982M:=
> Tue Jul 22 10:14:59 CDT 2014 =20
> root@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER amd64
> borg.lerctr.org /home/ler $ ssh tbh uname -a
> FreeBSD thebighonker.lerctr.org 10.0-STABLE FreeBSD 10.0-STABLE #39
> r269019M: Wed Jul 23 11:44:35 CDT 2014 =20
> root@thebighonker.lerctr.org:/usr/obj/usr/src/sys/GENERIC amd64
> borg.lerctr.org /home/ler $
>=20
Try adding -v to the 'zfs send' and see if it gives you more detail.
Can you also try this script for the replication:
http://github.com/allanjude/zxfer
--=20
Allan Jude
--onGXlbDDQmSsE6c7p32TBCccxd0ED6Sqx
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJT0USPAAoJEJrBFpNRJZKfvnsP/ijWQlG578gegPIY3N5e4Ut2
ZnIERSpvKXmhSjB0FiaTbQMiYGRgs1cZCLzVqhANjKRBRAT9n9OgyuYjPpOhsuHv
6DOJJ3sC66PoayKMML9mrPDac0aFm1Yz5c5JBl/6r3veTqzYh6Ex0rnqyDK/nFPk
Bzu1m6YyGLi4jt6wVGnYNB+rKMIWszJQu+KDzvd+nm7NfyPVkVdNsIfpgI178Q07
caJK9CIgIPVpVZ7CJQ0N3QU/pn/8eA5sh7VAibQv5tyNPVEkic7N8oE02w8VJuZy
5F4oQmSZReoP0aMwYB8FE0NIyCpISIcpkDu1cvMer0IpvBFnAixpto3tOmelnIri
RCqAK70sVNKqtyDO671/OgJECYo2cWR51BjUeFQql+Hl0aoo207Mn/YuNagMDp0n
9lIVPOmhn0Wy76oplEP13mnJWsbH51HLtuprA5pIbA+04laXghf6tFZLOPSunqY4
duFdrhLVlH54iVkR5n2SA9qmCUqUAcSRtxt6QwZySkHuG7UGLn1J/WicTHQqtO2a
qwFOlEn2zhIZh3zSscXWZEqEmABOKYV0erzBD8ZurMdDEblDrhJY6oC1PSY45OVP
L9rlfFAYQDEAex1tx8yRNLskzX6TZfqtVYGhd7Na2pKAXqt/lgz2UrKa1dNnuKNI
23NhWgNTudyAYTsPFJPc
=fS7y
-----END PGP SIGNATURE-----
--onGXlbDDQmSsE6c7p32TBCccxd0ED6Sqx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D1448C.40908>