You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The items generated by curveadm was not cleaned when execute "curveadm clean", which will cause system reboot into emergency mode if those disks were removed from host
#147
Closed
legionxiong opened this issue
Nov 4, 2022
· 2 comments
New items of fstab will be generated when deploy curvebs cluster via curveadm, the system will reboot into emergency mode once the disk recorded in fstab was removed. This is not a good design, store the disk mounting information into the database of curveadm and mount disk while starting curvebs would be better.
The text was updated successfully, but these errors were encountered:
legionxiong
changed the title
The items generated by curveadm was not cleaned when execute "curveadm clean", which will cause system reboot into emergency mode if those disks are removed
The items generated by curveadm was not cleaned when execute "curveadm clean", which will cause system reboot into emergency mode if those disks are removed from host
Nov 4, 2022
legionxiong
changed the title
The items generated by curveadm was not cleaned when execute "curveadm clean", which will cause system reboot into emergency mode if those disks are removed from host
The items generated by curveadm was not cleaned when execute "curveadm clean", which will cause system reboot into emergency mode if those disks were removed from host
Nov 4, 2022
New items of fstab will be generated when deploy curvebs cluster via curveadm, the system will reboot into emergency mode once the disk recorded in fstab was removed. This is not a good design, store the disk mounting information into the database of curveadm and mount disk while starting curvebs would be better.
The text was updated successfully, but these errors were encountered: