<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div><!--StartFragment--><pre><!--StartFragment--></pre><pre>Roland wrote:<br>> I'm surprised it even works that well. Snapshots in the Proxmox plugin > are very very limited: > - You can take a snapshot from the GUI, and it hopefully results in a > snapshot on LINSTOR level. > > And that's it. End of story. No rollback. Let alone over resizes.<br>> meant as last resort if everything is broken and the last resort is<br><!--StartFragment-->> rolling back to a snapshot and handling the rest manually on the CLI<br>> (including full resyncs and everything that might be necessary on the<br>> way). It is just for "ok cool, somewhere there is a snapshot and I did <br>> not loose my complete data"). No GUI, no nothing. Everything that works <br>> beyond what I described is pure coincidence and unsupported as well as <br>> untested. <br>> <br><br>Thank you Roland for your answer but maybe I expressed myself badly or I misunderstood.<br>I take snapshots through the graphical interface, this results in a snapshot at LINSTOR level (except by unchecking the RAM where only one LV is created).<br>Restorations are always carried out by the simple command "linstor s rb" without anything else.<br>It works on proxmox 5 and 6 (snapshot with or without RAM)<br>This should not be the case, additional precautions or operations may be necessary after the roll-back (manual resynchro ...)?<br>Shouldn't these snapshots be considered "reliable" and should only be used in the event of a desperate situation with no guarantee?<br><br>Regarding disk resizing in the graphical interface, this function is not supported by the Linstor pluggin?<br>It works on proxmox 5 and 6 / Drbd LVM or Thin but it would be a coincidence?<br><br>So, are my controller service problems that don't start related to this?<br><br>Thanks,<br><!--StartFragment--></pre><!--EndFragment--></div></div></body></html>