TOS5 re-mounts /home to new Volume
Posted: 13 Nov 2022, 10:44
Using F5-221 with TOS5 5.0.176 .
Volume1 is on SSDs, Volume2 is on 5400rpm drives.
When I add a new Volume2 from new Storage Pool, TOS5 remaps /home from Volume1 to point it to new Volume2. In the process anything previously saved under /Volume1/home disappears including all VMs for VirtualBox and others. Only way to recover is to ssh and move files over to Volume2.
Is this intentional, what would be the rationale for doing this, and how do I stop it? I don't want my /home to be on Volume2.
There are ways to remap other shared folders between Volumes, why not /home ?
Volume1 is on SSDs, Volume2 is on 5400rpm drives.
When I add a new Volume2 from new Storage Pool, TOS5 remaps /home from Volume1 to point it to new Volume2. In the process anything previously saved under /Volume1/home disappears including all VMs for VirtualBox and others. Only way to recover is to ssh and move files over to Volume2.
Is this intentional, what would be the rationale for doing this, and how do I stop it? I don't want my /home to be on Volume2.
There are ways to remap other shared folders between Volumes, why not /home ?