Hi,
great, thank you. So ZFS isn't picky about finding the target fs already
created and attributed when replicating data into it.
This is very cool!
Best regards,
Constantin
Darren J Moffat wrote:
> Constantin Gonzalez wrote:
>> Hi Darren,
>>
>> thank you for the clarification, I didn't kn
Constantin Gonzalez wrote:
> Hi Darren,
>
> thank you for the clarification, I didn't know that.
>
>> See the man page for zfs(1) where the -R options for send is discussed.
> Back to Brad's RFS, what would one need to do to send a stream from a
> compressed filesystem to one with a different c
Hi Darren,
thank you for the clarification, I didn't know that.
> See the man page for zfs(1) where the -R options for send is discussed.
oh, this is new. Thank you for bringing us -R.
Back to Brad's RFS, what would one need to do to send a stream from a
compressed filesystem to one with a diff
Constantin Gonzalez wrote:
> Hi Brad,
>
> this is indeed a good idea.
>
> But I assume that it will be difficult to do, due to the low-level nature
> of zfs send/receive.
>
> In your compression example, you're asking for zfs send/receive to
> decompress the blocks on the fly. But send/receive o
Hi Brad,
this is indeed a good idea.
But I assume that it will be difficult to do, due to the low-level nature
of zfs send/receive.
In your compression example, you're asking for zfs send/receive to
decompress the blocks on the fly. But send/receive operates on a lower
level: It doesn't care muc
I love the send and receive feature of zfs. However, the one feature
that it lacks is that I can't specify on the receive end how I want
the destination zfs filesystem to be be created before receiving the
data being sent.
For example, lets say that I would like to do a compression study to
d
