[manila] LVM shares are unmounted on reboot
Dear All, One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points. I use LVM Driver with DHSS=False. default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila [lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt After the reboot LVMs are there but they are mounted on their respective share location. Any way to solve this and this to be done automatically? Regards, Vaibhav
Hello! I believe there is not an automated way to do this using Manila itself, or a config thing you could set, considering that the controller will have no visibility over all mounts consuming the volume. So the consumers will need to re-mount, and even if scripted or automated, it should be triggered on each client consuming the share, which is painful. There might be more users that faced this issue in the past and could have a way to work it around, so getting some more input from other people would be appreciated. Regards, carloss Em ter., 30 de ago. de 2022 às 02:01, Vaibhav <mmilan2006@gmail.com> escreveu:
Dear All,
One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points.
I use LVM Driver with DHSS=False.
default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini
auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila
[lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt
After the reboot LVMs are there but they are mounted on their respective share location.
Any way to solve this and this to be done automatically?
Regards, Vaibhav
There is a chance that I have misinterpreted the email.
After the reboot LVMs are there but they are mounted on their respective share location. They are or they are not?
What I am getting now is: you rebooted the system and the Manila export locations are not matching the share location anymore. Is this correct? If so, Manila should be taking care of this. When the driver starts up, it runs a routine to fetch all shares and ensure the export location for all of them. Em seg., 5 de set. de 2022 às 18:21, Carlos Silva <ces.eduardo98@gmail.com> escreveu:
Hello!
I believe there is not an automated way to do this using Manila itself, or a config thing you could set, considering that the controller will have no visibility over all mounts consuming the volume.
So the consumers will need to re-mount, and even if scripted or automated, it should be triggered on each client consuming the share, which is painful. There might be more users that faced this issue in the past and could have a way to work it around, so getting some more input from other people would be appreciated.
Regards, carloss
Em ter., 30 de ago. de 2022 às 02:01, Vaibhav <mmilan2006@gmail.com> escreveu:
Dear All,
One of the host running Manila-share service has rebooted. After the reboot the LVMs are not mounted on the Manila mount points.
I use LVM Driver with DHSS=False.
default_share_type = default_share_type share_name_template = manila-%s rootwrap_config = /etc/manila/rootwrap.conf api_paste_config = /etc/manila/api-paste.ini
auth_strategy = keystone my_ip=192.168.82.2 enabled_share_backends = lvm enabled_share_protocols = NFS state_path=/var/lib/manila
[lvm] share_backend_name = LVM share_driver = manila.share.drivers.lvm.LVMShareDriver driver_handles_share_servers = False lvm_share_volume_group = VGZunManila lvm_share_export_ips = 192.168.82.2 lvm_share_export_root = $state_path/mnt
After the reboot LVMs are there but they are mounted on their respective share location.
Any way to solve this and this to be done automatically?
Regards, Vaibhav
participants (2)
-
Carlos Silva
-
Vaibhav