You should also be able to use the ZFS send/receive feature to send that pool
or data set to another node, and then send it back. It’s unclear why you are
draining it and recreating it, but if you are replacing the storage underneath,
you can send the dataset somewhere else (another OSS node
Thank you, Andreas. As always, your answers are the best.
bob
On 1/13/2016 10:14 PM, Dilger, Andreas wrote:
On 2016/01/12, 12:50, "lustre-discuss on behalf of Bob Ball"
wrote:
I have a zfs OST that I need to drain and
We’ve all done that at one point or another. Read the man page of ZFS. It
saves you from having to do a backup/restore, as it will send the entire data
set to another host. Depending on how much storage you have available (or how
full your file system is) you may not even have to drain it
I have to re-create because I borked up the underlying disks when they
were first configured, leaving a singleton disk in the pool with no
replica, and I'm also replacing them all with larger disks.
I was un-aware of the send/receive feature. I'll have to look into it.
Thanks for your input.
On 2016/01/14, 09:27, "Bob Ball" wrote:
>Thank you, Andreas. As always, your answers are the best.
In this case, I think Marc's answer is better. I didn't realize that you
are moving the OST over to new hardware and not retiring it permanently,
in which case moving the
On 2016/01/12, 12:50, "lustre-discuss on behalf of Bob Ball"
wrote:
>I have a zfs OST that I need to drain and re-create. This is lustre
>2.7.x. In the past, with ldiskfs OST, I did this a number of times
>following critical