On Mar 29, 2012, at 5:11 PM, Richard Elling wrote:
>> Thank you very much Ian and Carsten. Well, adding a -v gave me a clue. Turns
>> out that one of the old snapshots had a clone created.
>>
>> zfs receive -v was complaining that it couldn't destroy an old snapshot,
>> which wasn't visible
On Mar 29, 2012, at 4:33 AM, Borja Marcos wrote:
>
> On Mar 29, 2012, at 11:59 AM, Ian Collins wrote:
>
>> Does zfs receive produce any warnings? Have you tried adding -v?
>
> Thank you very much Ian and Carsten. Well, adding a -v gave me a clue. Turns
> out that one of the old snapshots had
On Mar 29, 2012, at 11:59 AM, Ian Collins wrote:
> Does zfs receive produce any warnings? Have you tried adding -v?
Thank you very much Ian and Carsten. Well, adding a -v gave me a clue. Turns
out that one of the old snapshots had a clone created.
zfs receive -v was complaining that it coul
-Original message-
To: zfs-discuss@opensolaris.org;
From: Borja Marcos
Sent: Thu 29-03-2012 11:49
Subject:[zfs-discuss] Puzzling problem with zfs receive exit status
>
> Hello,
>
> I hope someone has an idea.
>
> I have a replication program that cop
On 03/29/12 10:46 PM, Borja Marcos wrote:
Hello,
I hope someone has an idea.
I have a replication program that copies a dataset from one server to another
one. The replication mechanism is the obvious one, of course:
zfs send -Ri from snapshot(n-1) snapshot(n)> file
scp file remote machine
Hello,
I hope someone has an idea.
I have a replication program that copies a dataset from one server to another
one. The replication mechanism is the obvious one, of course:
zfs send -Ri from snapshot(n-1) snapshot(n) > file
scp file remote machine (I do it this way instead of using a pipel
