Experiments with exporting and importing a volume in OS6.7.1+

I have not tried it on a JBOD volume.  Will try to make some time to try it.  I have done it on RAID1 and RAID5,

This does have more applicability for a NAS with an EDA500 or a system with lots of bays where you may want more than one volume (like a 12-bay rack mount system).

I look at it this way:  Have a backup in case it blows up on you.  But if it works, it's a much faster way to transfer data from one NAS to another than over the network or backup and restore.  I'm moving backup volumes from two legacy 6-bay units to one 4200 (all upgraded to OS6) and plan to go this route.

BTW, I did find a way to successfully rename a volume via SSH.  It worked for me more than once, but I make no guarantees it will for you.

• btrfs filesystem show - this will list the volumes.  Assuming default volume data, one will have a random 8-digit hex number (at least I think it's random) followed by :data.
• btrfs filesystem label  /data  12345678:data1 - assumes default volume data, random hex value from above is 12345678, and renaming to data1.
• btrfs filesystem show - make sure the relabeling "took".  Double-check the hex value.
• vi  /etc/fstab - or use nano or your favorite editor you've installed to change the line that includes data to data1 (in two places)
• cat  /etc/fstab - check your editing.
• Reboot. 

If you get the dreaded "Management system is offline" in RAIDar, then SSH back in and verify btrfs filesystem show and cat /etc/fstab agree on volumes (except root is not listed in fstab).  Make sure there isn't still an entry for the old data volume in fstab.  Relabel again and/or re-edit fstab it if there are any discrepancies.  I did this process a few times, and one time I ended up still having the old volume along with the new one in fstab and it gave me that error.  I intentionally made the label and fstab not match and also got the error, but then verified that it's recoverable by fixing the error after the reboot and rebooting again.