On 06/29/2015 04:53 PM, John Andersen wrote:
On 06/29/2015 02:48 PM, Chris Murphy wrote: <snip>
btrfs-progs 4.1 now has a way to change the fs volume UUID. So after cloning if there is *any* possibility the two file systems will be visible to the kernel at the same time while one will be mounted, first it's best to change the UUID on one of them. This will take a while as the fs volume UUID is used constantly in the metadata format. In effect the whole fs (minus data) has to be read and written.
There might still be bugs, but another way to clone a Btrfs volume is the seed device. Make A a seed device, and it mounts read-only, add a new device to the volume, then umount and remount, and it mounts read-write, then delete the seed device and data is migrated to the new device. But also, the UUID is unique on the new device. After it's completely, the seed device can be made a non-seed volume again (no longer mounts read only).
<snip>
JA, Haven't you figured it out yet? It's a plot I tell ya'. In order to preserve data integrity, we are supposed to spend every hour of every day keeping up with so-call 'advancements' in new filesystems to the point that nefarious interests can easily mount a world takeover without notice or resistance. Resistance is futile.... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org