Date: Fri, 26 Feb 2016 10:35:30 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: ZFS full system backup hoses the backup host. Message-ID: <56D070C2.6060903@freebsd.org> In-Reply-To: <56D0284E.3010808@rlwinm.de> References: <CACpH0Me58jK%2BOz3PCqH93NEn=5V1SKwPGdku62sAVLVh%2BWxEeA@mail.gmail.com> <56CF6FB0.1010001@freebsd.org> <56D0284E.3010808@rlwinm.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OemQasB3JeWIAQn0aqncH1UeHLr5fLQ2i From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Message-ID: <56D070C2.6060903@freebsd.org> Subject: Re: ZFS full system backup hoses the backup host. References: <CACpH0Me58jK+Oz3PCqH93NEn=5V1SKwPGdku62sAVLVh+WxEeA@mail.gmail.com> <56CF6FB0.1010001@freebsd.org> <56D0284E.3010808@rlwinm.de> In-Reply-To: <56D0284E.3010808@rlwinm.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2016-02-26 05:26, Jan Bramkamp wrote: > On 25/02/16 22:18, Allan Jude wrote: >> On 2016-02-25 15:58, Zaphod Beeblebrox wrote: >>> This violated POLA for me. I backed up a host using: >>> >>> time zfs send -vRI @backup-1-e zroot@backup-1-f | ssh backuphost "zfs= >>> receive -vFud zroot/backup/host" >>> >>> >>> Only to find that the backup host (a week later) failed to reboot? T= he >>> problem? Well... -u on receive marks the filesystem as unmounted onl= y >>> "right now" not "next reboot" and -R on send implies -p (send dataset= >>> attributes) and... >>> >>> ... zroot/ROOT/default mountpoint=3D/ (among others). >>> >>> The only hackish way to fix this I see is to have a list of >>> mountpoints to >>> correct --- which is partially what I'm trying to avoid by using -R >>> --- I >>> just want the whole thing backed up. >>> >>> What have other people done to get around this and/or can we either >>> put in >>> an "ignore properties" on receive flag or a -R on send that doesn't s= end >>> them? >> >> The sysutils/zxfer script allows you to override properties during >> replication, so I usually set readonly=3Don and for such a backup woul= d >> set mountpoint=3Dnone >=20 > Do you know if this is race free or is there a moment on the receiving > system where it has an (unmounted) dataset with mountpoint=3D/ which wo= uld > break the system (possibly in interesting ways) after a crash? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" With zxfer this does not happen, because it creates the empty dataset, then manually copies the permissions. --=20 Allan Jude --OemQasB3JeWIAQn0aqncH1UeHLr5fLQ2i 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) iQIcBAEBAgAGBQJW0HDCAAoJEBmVNT4SmAt+hN0QALLgxL/mCqeTeHGVZ7w5vk9h /ElqFG4s/EfEIy2SIHZtkDgKqIUm7Qzbf4Rh8kAS+6hxExXVi0qwLHL5NtAE4rf3 8ALQUfWgGXXBB2H4sg/M/qEsheuzWwwuM13n0zKVyS/H7GICblxasscUyYGMT+9D TMkvoTRpDlLgWD+dFLS8ewNir9x6FIZXDMLvb5ywc6Iosdy4fUwN6FqaG27fs/Rd joBQlqhSk5/HC+UrT3dVJm5ULbvZW7HnLVNp4H/fAv9xOHjqsMHtlHBXWl0TBWG5 yfvhcfRfuZTx2tTpQRSI66Vvs2reO6rBNcBnC898s+lvtzS/Qn+d3E0WuD//2vXG fe6L8mXecNeGZvHu2OypdvD3thlTXCWqqAH3kg0RwYP1KiSQIWg4bF5S5N7x28bI FH7ywhBUHXH4WuEdKDhQmIHA2dcehqZyOi3bsfUeiKPXwXmDc8NdwsAUPbX43hgj I0Oxtn8dUAcZk39ggcbG81ssZ/XX7DOtf/rjl+TooOcFTJOE/9wd7H3MrrrpxYwW cOB3z2R14Azq7jueiAGXPDL/C+VH8hfIautkVtc/6IStrsOo7VreC16JylXaD7Ei OAMR/MIZVmYtfY0F2cSt63MCj4TmUNoqD0UxQxSgaPrJsb7XTNMq0u6Jr/drZ4QL Q3ft/apVaStVDkF/c4oJ =Pvf3 -----END PGP SIGNATURE----- --OemQasB3JeWIAQn0aqncH1UeHLr5fLQ2i--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56D070C2.6060903>