Matthew Ahrens wrote:
now wouldnt it be more natural way of usage when I intend to create a
clone, that by default
the zfs clone command will create the needed snapshot from the current
image internally as part
of taking the clone unless I explicitely specify that I do want to
take a clone of a
Frank Batschulat wrote:
it seems taking a clone always requires taking a snapshot first and provide
this as a parameter
to the zfs clone command.
now wouldnt it be more natural way of usage when I intend to create a clone,
that by default
the zfs clone command will create the needed snapshot f
it seems taking a clone always requires taking a snapshot first and provide
this as a parameter
to the zfs clone command.
now wouldnt it be more natural way of usage when I intend to create a clone,
that by default
the zfs clone command will create the needed snapshot from the current image
int
On Fri, 2006-09-01 at 06:03 -0700, Marlanne DeLaSource wrote:
> As I understand it, the snapshot of a set is used as a reference by
> the clone.
>
> So the clone is initially a set of pointers to the snapshot. That's
> why it is so fast to create.
>
> How can I "separate" it from the snapshot ? (
Marlanne DeLaSource wrote:
As I understand it, the snapshot of a set is used as a reference by the clone.
So the clone is initially a set of pointers to the snapshot. That's why it is
so fast to create.
How can I "separate" it from the snapshot ? (so that df -k or zfs list will
display for a
As I understand it, the snapshot of a set is used as a reference by the clone.
So the clone is initially a set of pointers to the snapshot. That's why it is
so fast to create.
How can I "separate" it from the snapshot ? (so that df -k or zfs list will
display for a 48G drive
pool/fs1 4G 40G
poo
