Re: [zfs-discuss] snapshots send/recv

[Brandon High]

On Sat, May 22, 2010 at 9:08 PM, Thomas Burgess  wrote:
> ok, so forcing just basically makes it drop whatever "changes" were made
> Thats what i was wondering...this is what i expected

If you're doing 'zfs send -i @first tank/foo/b...@second | zfs recv -F
newtank/foo/bar' then 'zfs recv -F' is the same as doing 'zfs rollback
newtank/foo/b...@first'. Any changes made on the newtank dataset will
be lost.

If you've done any snapshots on the received dataset (which is easy to
do if you have the auto-snap service running) -F will not delete them.
You'll have to manually go in and rollback datasets to the start
snapshot.

-B

-- 
Brandon High : bh...@freaks.com
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] snapshots send/recv

[Thomas Burgess]

ok, so forcing just basically makes it drop whatever "changes" were made

Thats what i was wondering...this is what i expected


On Sun, May 23, 2010 at 12:05 AM, Ian Collins  wrote:

> On 05/23/10 03:56 PM, Thomas Burgess wrote:
>
>> let me ask a question though.
>>
>> Lets say i have a filesystem
>>
>> tank/something
>>
>> i make the snapshot
>>
>> tank/someth...@one
>>
>> i send/recv it
>>
>> then i do something (add a file...remove something, whatever) on the send
>> side, then i do a send/recv and force it of the next filesystem
>>
>>  What do you mean "force it of the next filesystem"?
>
>
>  will the new recv'd filesystem be identical to the original forced
>> snapshot or will it be a combination of the 2?
>>
>
> The received filesystem will be identical to the sending one.
>
> --
> Ian.
>
>
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] snapshots send/recv

[Ian Collins]

On 05/23/10 03:56 PM, Thomas Burgess wrote:

let me ask a question though.

Lets say i have a filesystem

tank/something

i make the snapshot

tank/someth...@one

i send/recv it

then i do something (add a file...remove something, whatever) on the 
send side, then i do a send/recv and force it of the next filesystem



What do you mean "force it of the next filesystem"?

will the new recv'd filesystem be identical to the original forced 
snapshot or will it be a combination of the 2?


The received filesystem will be identical to the sending one.

--
Ian.

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] snapshots send/recv

[Thomas Burgess]

oh, this makes sense

let me ask a question though.

Lets say i have a filesystem

tank/something

i make the snapshot

tank/someth...@one

i send/recv it


then i do something (add a file...remove something, whatever) on the send
side, then i do a send/recv and force it of the next filesystem

will the new recv'd filesystem be identical to the original forced snapshot
or will it be a combination of the 2?


On Sat, May 22, 2010 at 11:50 PM, Edward Ned Harvey
wrote:

> > From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> > boun...@opensolaris.org] On Behalf Of Thomas Burgess
> >
> > but i get an error:
> >
> > cannot receive incremental stream: destination tank/nas/dump has been
> > modified
> > since most recent snapshot
>
> Whenever you send a snap, and you intend to later receive an incremental,
> just make the filesystem read-only, to ensure you'll be able to receive the
> incremental later.
>
> zfs set readonly=on somefilesystem
>
>
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] snapshots send/recv

[Edward Ned Harvey]

> From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
> boun...@opensolaris.org] On Behalf Of Thomas Burgess
> 
> but i get an error:
> 
> cannot receive incremental stream: destination tank/nas/dump has been
> modified
> since most recent snapshot

Whenever you send a snap, and you intend to later receive an incremental,
just make the filesystem read-only, to ensure you'll be able to receive the
incremental later.

zfs set readonly=on somefilesystem

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] snapshots send/recv

[Thomas Burgess]

On Sat, May 22, 2010 at 9:26 PM, Ian Collins  wrote:

> On 05/23/10 01:18 PM, Thomas Burgess wrote:
>
>>
>> this worked fine, next today, i wanted to send what has changed
>>
>> i did
>> zfs snapshot tank/nas/d...@second
>>
>> now, heres where i'm confusedfrom reading the man page i thought this
>> command would work:
>>
>> pfexec zfs send -i tank/nas/d...@first tank/nas/d...@second| ssh
>> wonsl...@192.168.1.15  "/bin/pfexec
>> /usr/sbin/zfs recv -vd tank/nas/dump"
>>
>>  It should (you can shorten the first snap to "first".
>
>
>> but i get an error:
>>
>> cannot receive incremental stream: destination tank/nas/dump has been
>> modified
>> since most recent snapshot
>>
>>  Well has it?  Even wandering around the filesystem with atime enabled
> will cause this error.
>
> Add -f to the receive to force a roll-back to the state after the original
> snap.
>
> Ahh, this i didn't know. Yes, i DID cd to the dir and check some stuff and
atime IS enabledthis is NOT very intuitive.

adding -F worked...thanks




> --
>
> Ian.
>
>
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Re: [zfs-discuss] snapshots send/recv

[Ian Collins]

On 05/23/10 01:18 PM, Thomas Burgess wrote:


this worked fine, next today, i wanted to send what has changed

i did
zfs snapshot tank/nas/d...@second

now, heres where i'm confusedfrom reading the man page i thought 
this command would work:


pfexec zfs send -i tank/nas/d...@first tank/nas/d...@second| ssh 
wonsl...@192.168.1.15  "/bin/pfexec 
/usr/sbin/zfs recv -vd tank/nas/dump"



It should (you can shorten the first snap to "first".


but i get an error:

cannot receive incremental stream: destination tank/nas/dump has been 
modified

since most recent snapshot

Well has it?  Even wandering around the filesystem with atime enabled 
will cause this error.


Add -f to the receive to force a roll-back to the state after the 
original snap.


--

Ian.

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

[zfs-discuss] snapshots send/recv

[Thomas Burgess]

I'm confusedI have a filesystem on server 1 called tank/nas/dump

I made a snapshot called first

zfs snapshot tank/nas/d...@first

then i did a zfs send/recv like:

zfs send tank/nas/d...@first | ssh wonsl...@192.168.1.xx "/bin/pfexec
/usr/sbin/zfs recv tank/nas/dump"


this worked fine, next today, i wanted to send what has changed

i did


zfs snapshot tank/nas/d...@second


now, heres where i'm confusedfrom reading the man page i thought this
command would work:


pfexec zfs send -i tank/nas/d...@first tank/nas/d...@second| ssh
wonsl...@192.168.1.15 "/bin/pfexec /usr/sbin/zfs recv -vd tank/nas/dump"



but i get an error:

cannot receive incremental stream: destination tank/nas/dump has been
modified
since most recent snapshot


why is this?
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss