-
-
Notifications
You must be signed in to change notification settings - Fork 662
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
Make LVM snapshot default when no issues get reported #1986
Comments
I'd say when development stopped on that part for some time because it's rock solid, then maybe. :) |
I'd say it is already pretty stable but yeah |
We could do this for Ubuntu 22.04 making the OS disk 45 GB in size, or extend the drive so there's only 5 GB left and keep it 40 GB in total size. Would that work? |
cc @small1 |
From my side, yes 👍 |
Just tested on one of my prod instances. I don't think this is stable enough:
|
Honestly, I've never seen this issue. What did you do before this issue appeard? |
This way I'am running this setup since half a year or longer without any issue... |
Or in other words: what are the steps to reproduce this issue? |
Yes, since the company was sold, we moved the whole thing to a new server with a new install and export import of DB and stuff. So it's by the book installed "your way".
I don't know. I just ran an update yesterday and it happened. No automatic updates either. |
Thanks! So then I will try to investigate how this could happen :) |
Does it happen every time you run the update script? |
Could be a bug with lvm... Could you please try the following commands and post the output of those here (if it should still happen)?
|
@enoch85 do you have some feedback here? It is hard to debug without a way to reproduce this issue... |
As it's not in the released version yet, please add a PR with the fix you proposed, and I'll run one of the auto update VMs with the new setup. |
I've only seen this once, and I'm not sure if the server was rebooted or not. If you think it can be improved, then do so, else leave it for now. |
Thanks for the feedback! |
I'm still not convinced it should be the default way of the VM. One more thing that could break - we want to keep those events limited. |
Some debug output:
|
Thanks for the verbose output! Please try the following and report back:
|
Already rebooted ;/ |
hm :/ |
When I have the output it should only take one command to remove the blocking device and afterwards the lvremove should finally work :) |
|
Thanks! after runing the following command, the removal should work. please report back!
|
If that works, I will try to come up with a PR that fixes this once and for all :) |
Thanks for looking into this! |
Still same issue! :( |
I really hoped that this would solve the peoblem. (I followed the steps from the guide that I linked above). Seems like there is unfortunately still no way around a restart then :( |
Don't know how "safe" this is, but it works:
https://antnix07.blogspot.com/2018/02/lvmdevice-mapper-remove-ioctl-on-failed.html |
Resuled in this error: |
Hehe, that command removed the whole snapshot thing. It never does snapshots anymore after that. :D |
Yeah, so I still think that this is some kind of issue of lvm. I hope that this will be solved with ubuntu 22.04 but I guess we'll see. |
nice to know if thats desired ;) |
@szaimen Maybe if we name the snapshot to something random like |
Problem is that we use that name for locking so that no further backup or e.g. update gets started if that snapshot exists so this would probably need some (or a lot of) refactoring. Also is this clearly a bug in LVM if snapshot removal is not working so I'd rather wait for a new Ubuntu version and hope that it is fixed there. |
Ubuntu 22.04 is out, same thing still... How should we proceed? Leaning towards closing and removing the function all together. Or, add a notification that you need to reboot. |
That would break all backup scripts so please don't do this.
Sounds good but there is one already here? Lines 156 to 164 in f1ff45f
|
Should we improve the notification maybe somehow? |
I vote for improve notification, and force reboot if LVM snapshots are made. |
Do you have some suggestion how to improve it?
So directly after the update script then or when should the reboot happen? |
Yes, if LVM snapshot is enabled and a snapshot exist.
Just add another |
Hello, I'm getting this at new install on ubuntu 22.04.2 LTS when chosing yes for LVM snapshots right in the second question. nextcloud_install_production.sh: line 113: [: 18,4: integer expression expected nextcloud_install_production.sh: line 113: [: 50,4: integer expression expected |
Hi, can you post the output of |
I'm getting |
Fix is in #2510 |
Hi, I know this option isn't default yet, but when you installing the VM with your scripts, first you're asking if all disk space should be used and after this you want to create the snapshots which is failing if you said yes before because of insufficient disk space. |
This is just a reminder that we don't forget to make the LVM snapshot default when no issues get reported.
vm/nextcloud_install_production.sh
Line 68 in 39e64fe
After we do this, everyone wil be able to use the built-in backup solution.
The text was updated successfully, but these errors were encountered: