[opensuse-factory] Snapper: cannot boot from any snapshots
Hi I am unable to boot from any snapshot. After selecting the option to boot from a read-only snapshot, and then selecting a snapshot, I see a message that says something like "if OK, run snapper rollback and reboot" but I can't do anything from there. Pressing enter refreshes the screen and I see the same message. I can enter the GRUB menu and such, I just can't actually boot. Obviously this is quite alarming as I'd always thought I can rely on Snapper and is one of the reasons I'm happy to use Tumbleweed. Any suggestions? Kind regards, Huw
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-02-25 01:14, huw wrote:
Are you sure that is not text mode Linux? A terminal? - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliw0vIACgkQja8UbcUWM1z5owD/bj4Dvbi2BnXP0DAUJliKwAgD YzdOuE3rxKeB3q6vnasBAIthEyoDobcT6fC77FcXlJFUwa6IG5oS2NxjZs6qM/rj =VnKi -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 00:42:26 GMT Carlos E. R. wrote:
I'm not sure what you mean...this is via the Grub menu when I first start my PC. Here's a screenshot: https://imgur.com/a/K7Fww I see this after I select which snapshot I want to boot from. Kind regards, Huw
On Saturday, 25 February 2017 01:14:22 CET huw wrote:
the snapshot boot is confusing. if i remember you select one of the snapshots, but the next option is something like "boot opensuse" i.e. no mention of snapshot anymore. If you keep trying to select the snapshot (which appears the natural choice) you go round in circles. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 08:02:01 GMT nicholas wrote:
Hmm....so does that mean that after seeing this screen: https://imgur.com/a/K7Fww ...I press escape to return to the original boot menu and just select the default boot option as if I wasn't using a snapshot? If so, how can I verify, after booting, that I'm in the snapshot? Kind regards, Huw
On Saturday, 25 February 2017 09:14:44 CET huw wrote:
i have just tested, i dont get the "if ok..." dialouge but have seen it before (it may come from selecting the wrong entry). 1 - from menu select roll back to snapshot 2 - select snapshot 3 - the screen now shows "bootable snapshot #num" as the top entry, second entry is "boot tumbleweed" -< select the *second* entry you will now get warning during boot that a file cannot be written. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 08:51:00 GMT nicholas wrote:
Well that isn't very intuitive! It does indeed work though (none of my snapshots result in a useable desktop but I guess that's a separate problem). Many thanks for testing this Nicholas, that was kind of you. Kind regards, Huw
On Saturday, 25 February 2017 10:18:44 CET huw wrote:
general comment - if the confusing dialouge is not a limitation of grub - *it should be changed* if you did want more help - can you describe the problem, assumed cause and what you mean by a usable desktop? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 10:03:53 GMT nicholas wrote:
Well, I didn't go into it at first because it's probably related to a recent zypper up I did with (unknowingly) a full root partition, which caused the upgrade to partially fail. But anyway, the problem is that when I boot from a snapshot I get as far as the grey screen with three green dots in the middle, and it doesn't go any further. I can use alt-f1 to switch to a console though. Is this working as intended, or should SDDM start? Kind regards, Huw
On Saturday, 25 February 2017 16:46:15 CET huw wrote:
your on tumbleweed with btrfs and your root is full? have you disabled quotas? what does "sudo btrfs filesystem usage -h /" say? can you also give output of "sudo snapper list" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 17:09:41 CET you wrote:
be carefull of writing ANYTHING else to the btrfs partition! (or solutions will get uglier) to save time - IF it is full : can you run "sudo snapper list" and if so remove snapshots using "sudo snapper rm num1-num2" [where num1 and num2 are a range of oldest snapshot numbers (not including 0 or 1 and not a few of the most recent ones)] ONLY IF you can remove sufficient snapshots (and this is the cause of no space) you should probably do a rebalance "sudo /etc/cron.weekly/btrfs-balance" (takes time), then "sudo zypper dup --no-allow-vendor-change" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 25. Februar 2017 17:15:21 MEZ schrieb nicholas <ndcunliffe@gmail.com>:
I was always wondering what happens if you delete the oldest snapshots - 0 and 1 Sure this is not possible? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 18:07:18 CET Axel Braun wrote:
I was always wondering what happens if you delete the oldest snapshots - 0 and 1 Sure this is not possible?
im sure deleting your root fs is possible, but not from snapper. from a live disk perhaps? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 25. Februar 2017 18:18:19 MEZ schrieb nicholas <ndcunliffe@gmail.com>:
Deleting a snapshot does not necessarily mean deleting the root fs. I can delete the oldest snapshot of, let's say a Virtualbox image, without harming the system. I just lose the old status. But I don't know if this is possible in btrfs. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 16:09:41 GMT nicholas wrote:
Yeah, the root was completely filled - at least according to df, which I have since learned may not be reliable on a btrfs partition, although when I last upgraded I had a whole slew of errors relating to the device being full. I already deleted some snapshots manually now, and have upgraded at least once since. However, the output of your command is: Overall: Device size: 29.30GiB Device allocated: 26.40GiB Device unallocated: 2.90GiB Device missing: 0.00B Used: 23.45GiB Free (estimated): 5.27GiB (min: 3.82GiB) Data ratio: 1.00 Metadata ratio: 2.00 Global reserve: 61.83MiB (used: 0.00B) Data,single: Size:24.34GiB, Used:21.96GiB /dev/sda4 24.34GiB Metadata,DUP: Size:1.00GiB, Used:759.55MiB /dev/sda4 2.00GiB System,DUP: Size:32.00MiB, Used:16.00KiB /dev/sda4 64.00MiB Unallocated: /dev/sda4 2.90GiB I have not knowingly disabled quotas - I wouldn't know how. Kind regards, Huw
On Saturday, 25 February 2017 18:14:33 CET huw wrote:
you say it was full, you deleted snapshots, have free space, and have upgraded (dup --no-allow-vendor-change) - so is it working? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 17:40:27 GMT nicholas wrote:
you say it was full, you deleted snapshots, have free space, and have upgraded (dup --no-allow-vendor-change) - so is it working?
Yeah - to be clear, I have a (seemingly) fully functional system right now. It's just that I would like the assurance that I will be able to roll back if I ever need to, hence my experiments with Snapper. At the moment, because the system doesn't fully boot (into SDDM and thence into KDE) from a snapshot I'm not convinced things would work if I attempted a rollback. Kind regards, Huw
On Saturday, 25 February 2017 19:02:49 CET huw wrote:
my head is spinning, but yes you should be able to login and go to a functioning desktop, however since you previously borked your system id try again with a new snapshot and if it dosnt work youve found a bug. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* huw <huw@synapticsilence.net> [02-25-17 13:28]:
and so you will report it ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 19:27:46 CET huw wrote:
I'd say the fact that Snapper was able to fill my root partition without quotas being disabled is a bug...
it is unfortunate yes, but a bug no - quotas works on the principle of using % (50% default) of free space, enforced on cron defined intervals. in your case you actually have *very* little free space, so if you hit it with file *changes* over a relativly short space of time it will fill up regardless. you have several options: change quota allocations, reduce number (range) of snapshots, increase space, etc -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 18:48:22 GMT nicholas wrote:
Perhaps technically not a bug then, but even so I feel like this shouldn't have been allowed to happen to a "normal" desktop user doing nothing exotic and accepting all defaults at install. Also, I notice there are no options in Yast2/Snapper to do any of what you suggest. Kind regards, Huw
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-02-25 18:14, huw wrote:
So, a 30 GiB root partition. That is way too little for btrfs, even more so on Tumbleweed. You should have 100 GiB at least. If you want snapshots, that is. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliyCjUACgkQja8UbcUWM1yC7wD+NbEzkEjAzK+cvol5sUcQjRL6 PTgKOcSQCYdt69aD/YQA/0TgrsC+K3TnNwj8nO0mMqbuhbXQf03iQQFyblF9I+gP =u9J6 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 22:50:29 GMT Carlos E. R. wrote:
Well, I accepted whatever was the default partition scheme during install. So, something the openSUSE team needs to change, I would have thought. At the very least, a message to the effect. 100GB is insane for a root partition for any other distro. Kind regards, Huw
On 2017-02-26 00:07, huw wrote:
...
The choice of distro has no relevance. If you use btrfs, you need at least double the space you would allocate. If you choose a distro that changes fast, then at least triple. That is my opinion. Others differ, but you can see what happened to you... -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))
On Saturday, 25 February 2017 23:19:10 GMT Carlos E. R. wrote:
And as I said: if that is the case, then it needs to be clear to users. Other distros *are* relevant because they will colour users' perception with regard to sensible root partition size.
That is my opinion. Others differ, but you can see what happened to you...
You seem to be implying that this is a mess of my own creation. If so, then yes, my opinion will differ *greatly* from yours. Huw
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-02-26 00:26, huw wrote:
I don't know what other distros do. I don't care, actually. What I say is that if they use btrfs with snapshots, the size has to be much bigger, or users will face the same issues as you did.
No, I didn't. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliyFE0ACgkQja8UbcUWM1y99QEAgzLcjqsah63+v+p37wmekUyE snPmmfzpuw4NubGCYQMA/Alq+Rn/WFThvo/4l6gdaXWBBWh43FgRtPbfKA0/4BiM =s6D8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday, 25 February 2017 23:50:29 CET Carlos E. R. wrote:
i disagree with 100gb (if you dont have root resident VMs etc), i have sufficient space with 26gb (30gb would probably be better) Overall: Device size: 25.97GiB Device allocated: 23.20GiB Device unallocated: 2.77GiB Device missing: 0.00B Used: 17.23GiB Free (estimated): 8.34GiB (min: 8.34GiB) Data ratio: 1.00 Metadata ratio: 1.00 Global reserve: 55.75MiB (used: 0.00B) PS it is trivial to expand btrfs even online (mounted) btrfs filesystem resize +2g / -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
26.02.2017 08:54, nicholas пишет:
PS it is trivial to expand btrfs even online (mounted)
The practical problem is to expand underlying storage, not filesystem itself. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday, 26 February 2017 07:35:39 CET you wrote:
wait... you mean make space available for the partition to expand, accepted! (if only you could edit an email once sent) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-02-26 06:54, nicholas wrote:
On Saturday, 25 February 2017 23:50:29 CET Carlos E. R. wrote:
You are running to close to the limit. Even on ext4, means you don't have /tmp space to burn a DVD.
PS it is trivial to expand btrfs even online (mounted) btrfs filesystem resize +2g /
If you have free disk. I'm assuming that it doesn't need to be contiguous space, I do not know. - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliy044ACgkQja8UbcUWM1wgmAD8Cii7O+ZGB6sjoHEv0vuLaxr2 UF0uKfkOTp4bP8IjKwYA/04cxnHR67ipv+aarTqEzZwPKR0C/eVSHR8Bw65fDpjx =ZSBu -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-02-26 14:14, Andrei Borzenkov wrote:
In principle it is possible to add another partition as second device. This is not supported by YaST though.
Like LVM? Now that I think. On SSD "contiguous space" has no meaning. We could virtually join space in partition 3 to partition 10 and reorder to be contiguous without moving any data. Create new bigger partition 3 any time. Has anybody designed for this? - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAliy1U0ACgkQja8UbcUWM1ymNQEAgyxYYGqHS0LYNkg5Oz88oJ4V xTOPppr/TMwcpUnY4t8A/0EWGTphU0HNrbxIv+VQ/6yjZQiF5rwHl3wRbbR1eBZf =1Gz8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
26.02.2017 16:17, Carlos E. R. пишет:
Not sure I understand the question. btrfs has multidevice support; it also has internal implementation of various raid levels. There is nothing new here. But YaST currently only supports single device btrfs. Situation is similar to using encrypted LUKS as root filesystem - it is possible but when using YaST.
Not sure what you mean with "reordering" but yes, on SSD logically concatenating multiple non-contiguous partitions should have no negative impact like on rotating disks.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2017-02-26 a las 16:28 +0300, Andrei Borzenkov escribió:
I meant that if you have a layout of partitions like this: 1 2 3 4 5 on an SSD disk and you want to join 1 and 5, they could be joined by the firmware, reordering the LBAs. Nah, brain fart. Forget it. :-) - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAli0vR4ACgkQja8UbcUWM1zIBQD9EwFY+kdBIqvSxl9N3IqEYtGN 0K0Akar0Tw1QZDpNC8sA/igp2gJ5UWrPpb5hr550RIYlEgUQ88otv20cs/jgPYjX =NmVR -----END PGP SIGNATURE-----
On Sunday, 26 February 2017 14:14:35 CET Andrei Borzenkov wrote:
its absolutly trivial to add non-continous space on btrfs (even if not supported by yast). [if i recall correctly you can even do online migration to a new partition] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
26.02.2017 16:35, nicholas пишет:
Yes, you can migrate by adding new device and then removing old one. Not sure whether you can replace device directly on non-redundant filesystem. Of course if this was root, you may have some useful bits (bootloader) outside of filesystem and that will not be migrated. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sat, 2017-02-25 at 11:03 +0100, nicholas wrote:
https://bugzilla.suse.com/show_bug.cgi?id=1027588 -- Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107 SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Andrei Borzenkov
-
Axel Braun
-
Carlos E. R.
-
huw
-
Martin Wilck
-
nicholas
-
Patrick Shanahan