- Joined
- Dec 11, 2015
- Messages
- 1,410
Hello,
I'm planning to add two special vdevs to my main pool.
To my understanding, in order to make use of them, I'd have to 'rewrite in situ' my pools data to populate the special vdevs.
What would be the most efficient way to do this?
A large chunk of my data is "too large to be doubled during a send/recv" but in turn, is 'user friendly' enough that it would not suffer from a
Other parts are more of 'block nature' that is, larger blobs owned and operated by a ProxmoxBackupServer for example. Towards these, I'm a hesitant even a
The other "potential" options would be ZFS send|recv, which would be nice for the 'owned blobs', but cannot be done on the overall pool due to space constraints.
Is there any "gotcha" to keep in mind when doing a zfs send/zfs recv on the same pool?
Here's a suggestions, would this be sufficient?
Noting that [zfs recv -nV] is a 'verbose dry run' that does not actually receive the dataset.
Any suggestions or input?
I'm planning to add two special vdevs to my main pool.
To my understanding, in order to make use of them, I'd have to 'rewrite in situ' my pools data to populate the special vdevs.
What would be the most efficient way to do this?
A large chunk of my data is "too large to be doubled during a send/recv" but in turn, is 'user friendly' enough that it would not suffer from a
rsync -r
.Other parts are more of 'block nature' that is, larger blobs owned and operated by a ProxmoxBackupServer for example. Towards these, I'm a hesitant even a
rsync --archive
is sufficiently safe.The other "potential" options would be ZFS send|recv, which would be nice for the 'owned blobs', but cannot be done on the overall pool due to space constraints.
Is there any "gotcha" to keep in mind when doing a zfs send/zfs recv on the same pool?
Here's a suggestions, would this be sufficient?
Code:
zfs snapshot tank/dataset@snapshot zfs send -R -I -v tank/dataset@snapshot | pv -Wbrft | zfs recv -s tank/newdataset
Noting that [zfs recv -nV] is a 'verbose dry run' that does not actually receive the dataset.
Any suggestions or input?