Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

lxd recover : 'mountpoint' does not apply to datasets of this type. #11984

Closed
StormYudi opened this issue Jul 10, 2023 · 5 comments · Fixed by #11991
Closed

lxd recover : 'mountpoint' does not apply to datasets of this type. #11984

StormYudi opened this issue Jul 10, 2023 · 5 comments · Fixed by #11991
Assignees
Labels
Bug Confirmed to be a bug

Comments

@StormYudi
Copy link

StormYudi commented Jul 10, 2023

Required information

  • Distribution: Ubuntu
  • Distribution version: Ubuntu 20.04 LTS
  • The output of "lxc info" or if that fails:
    • Kernel version: 5.4.0-153-generic
    • LXC version: 5.15-002fa0f
    • LXD version: 5.15-002fa0f
    • Storage backend in use: ZFS

Issue description

I lost my os disk recently, so I reinstall ubuntu with lxd on a new disk. I was trying to use lxd recover command to restore my data zfs pool. all containers, vm are here on the zfs pool named data.

root@rvh-1:/var/snap/lxd/common/lxd/storage-pools/data/containers# lxd recover
This LXD server currently has the following storage pools:
Would you like to recover another storage pool? (yes/no) [default=no]: yes
Name of the storage pool: data
Name of the storage backend (btrfs, ceph, cephfs, cephobject, dir, lvm, zfs): zfs
Source of the storage pool (block device, volume group, dataset, path, ... as applicable): data
Additional storage pool configuration property (KEY=VALUE, empty when done): zfs.pool_name=data
Additional storage pool configuration property (KEY=VALUE, empty when done): 
Would you like to recover another storage pool? (yes/no) [default=no]: 
The recovery process will be scanning the following storage pools:
 - NEW: "data" (backend="zfs", source="data")
Would you like to continue with scanning for lost volumes? (yes/no) [default=yes]: 
Scanning for unknown volumes...
Error: Failed validation request: Failed checking volumes on pool "data": Failed to run: zfs set mountpoint=legacy canmount=noauto data/custom/default_rvh2-epbackup: exit status 1 (cannot set property for 'data/custom/default_rvh2-epbackup': 'mountpoint' does not apply to datasets of this type)

data/custom/default_rvh2-epbackup is a custom volume of zfs, I use this volume to attach to one of my vm.

It seems that LXD is trying to execute a command which is not supported by ZFS?

my zfs list:
image

@tomponline
Copy link
Member

Please can you show the full zfs list -t all output?

Also, can you confirm if those volumes are block mode custom volumes?

@tomponline tomponline added the Incomplete Waiting on more information from reporter label Jul 11, 2023
@StormYudi
Copy link
Author

StormYudi commented Jul 11, 2023

Sorry the list is too long, so I uploaded that to ubuntu Pastebin:
https://pastebin.ubuntu.com/p/5XySMgKrjj/

I am pretty sure I create that volumes by the guide, so it should in block mode:
image

@tomponline tomponline added Bug Confirmed to be a bug and removed Incomplete Waiting on more information from reporter labels Jul 11, 2023
@tomponline
Copy link
Member

Thanks, so looks like lxd recover needs to learn how to handle custom block volumes.

@tomponline
Copy link
Member

@monstermunchkin please can you take a look at this and check its not a regression related to the changes we've made to zfs block mode filesystem volumes lately. Thanks

@StormYudi
Copy link
Author

If that is a bug, could we fix that ASAP?
Because it is our production server, or do we have other methods to skip unsupported volumes and recover other containers, and virtual machines first?

monstermunchkin added a commit to monstermunchkin/lxd that referenced this issue Jul 11, 2023
…volumes

This fixes an issue where custom block volumes would be listed as
datasets instead of volumes.

Fixes canonical#11984

Signed-off-by: Thomas Hipp <[email protected]>
monstermunchkin added a commit to monstermunchkin/lxd that referenced this issue Jul 12, 2023
…volumes

This fixes an issue where custom block volumes would be listed as
datasets instead of volumes.

Fixes canonical#11984

Signed-off-by: Thomas Hipp <[email protected]>
tomponline pushed a commit to tomponline/lxd that referenced this issue Sep 22, 2023
…volumes

This fixes an issue where custom block volumes would be listed as
datasets instead of volumes.

Fixes canonical#11984

Signed-off-by: Thomas Hipp <[email protected]>
tomponline pushed a commit to tomponline/lxd that referenced this issue Sep 22, 2023
…volumes

This fixes an issue where custom block volumes would be listed as
datasets instead of volumes.

Fixes canonical#11984

Signed-off-by: Thomas Hipp <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Confirmed to be a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants