search

oetiker / znapzend

zfs backup with remote capabilities and mbuffer integration.
www.znapzend.org
GNU General Public License v3.0
608 stars 138 forks source link

Manual Mountpoint for new subpools #436

Closed tyalie closed 3 years ago

tyalie commented 4 years ago

When znapzend creates a new subpool on the backup drive it doesn't set the mount point to legacy or so. This can create conflicts when importing the drive.

My configuration looks like this:

backup                     33.5G   865G  9.33G  /backup
backup/docker              4.37G   865G   528M  /backup/docker
backup/docker/container    1.72G   865G  1.71G  /backup/docker/container

I've also a folder named docker in the backup directory. When I now try to import the drive I get the error, that backup/docker can't be mounted, as the folder isn't empty. Interestingly the sub pool backup/docker/container also creates problems. I'm unsure why, but I've the suspicion, that zfs can't mount backup/docker after mounting backup/docker/container as the folder then isn't empty anymore.

If znapzend doesn't depend on the mount point I would suggest to set it to legacy, when creating a new pool on the backup drive.

stale[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.