Date: Wed, 20 Oct 2010 09:02:10 -0400 From: Derek Buttineau <derek@csolve.net> To: "Dan Langille" <dan@langille.org> Cc: Ruben de Groot <mail25@bzerk.org>, freebsd-stable@freebsd.org Subject: Re: 'zfs send -i': destination has been modified Message-ID: <130DC762-F43A-43CC-861F-0602E77D160E@csolve.net> In-Reply-To: <40c67a2c91813d90fa4a3dafb8604db1.squirrel@nyi.unixathome.org> References: <c00184baaf75b1e64e625a0b9dfb97b4.squirrel@nyi.unixathome.org> <20101020124434.GA41365@ei.bzerk.org> <40c67a2c91813d90fa4a3dafb8604db1.squirrel@nyi.unixathome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2010-10-20, at 8:54 AM, Dan Langille wrote: > Not that I know of. But I do think that is the issue. Thank you. = Adding > a -F option to the receive helps: >=20 > # zfs send -i storage/bacula@2010.10.19 storage/bacula@2010.10.20 | = zfs > receive -vF storage/compressed/bacula > receiving incremental stream of storage/bacula@2010.10.20 into > storage/compressed/bacula@2010.10.20 > received 20.0GB stream in 303 seconds (67.5MB/sec) >=20 > Just after I sent my email, I found this post: >=20 > = http://lists.freebsd.org/pipermail/freebsd-current/2007-July/075774.html >=20 > Problem solved. :) Good workaround, forcing the receive, but I'd still like to figure out = what's causing the filesystem to be modified on the receiving end. But = this will be useful if I can't determine what is causing it to differ. Thanks, Derek
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?130DC762-F43A-43CC-861F-0602E77D160E>