I have been running Tumbleweed on a iMac and it had been going great. The other day I was doing an update. When I checked progress, I saw that the power was off! It is not a laptop. I have no idea how the power could have been off. I have to boot with a previous kernel. And I do not get wlan. So I thought I would undo the changes with snapper. The new kernel stops when it accesses the initrd. Unfortunately, it complains that there are no configs. I have never seen an openSUSE install not set up snapper. Could this have happened? Or could it be that it lost the config info when things went bad? I really would like to recover this install. (Do I have a backup? Umm.... It is just a home system used as a convenience.No data to protect. But, yeah, I know...) Is there any way that I can determine if snapper was in fact set up, but that the config just lost? Or anything else I might do? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, 21 January 2018 13:36:06 CET Roger Oberholtzer wrote:
I have been running Tumbleweed on a iMac and it had been going great. The other day I was doing an update. When I checked progress, I saw that the power was off! It is not a laptop. I have no idea how the power could have been off.
I have to boot with a previous kernel. And I do not get wlan. So I thought I would undo the changes with snapper. The new kernel stops when it accesses the initrd.
Unfortunately, it complains that there are no configs. I have never seen an openSUSE install not set up snapper. Could this have happened?
Yes, can happen. If the root device is too small the installer suggests to not use snapshots and therefore no snapper config is created.
Or could it be that it lost the config info when things went bad?
I doubt this would happen.
I really would like to recover this install. (Do I have a backup? Umm.... It is just a home system used as a convenience.No data to protect. But, yeah, I know...)
Is there any way that I can determine if snapper was in fact set up, but that the config just lost? Or anything else I might do?
I recommend a rescue system, try to mount the existing partitions, chroot into the existing installation and check if everything that is expected is there, e.g. in /boot/ the kernel and initrd. You might be able to call `zypper dup` within the chroot to repair some missing packages in case the upgrade got interrupted. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jan 22, 2018 at 9:03 AM, Oliver Kurz <okurz@suse.de> wrote:
Unfortunately, it complains that there are no configs. I have never seen an openSUSE install not set up snapper. Could this have happened?
Yes, can happen. If the root device is too small the installer suggests to not use snapshots and therefore no snapper config is created.
The root partition is bigger than on other systems where this has been set up.
Or could it be that it lost the config info when things went bad?
I doubt this would happen.
One would think so. Otherwise there is a fundamental flaw in the system!
I recommend a rescue system, try to mount the existing partitions, chroot into the existing installation and check if everything that is expected is there, e.g. in /boot/ the kernel and initrd. You might be able to call `zypper dup` within the chroot to repair some missing packages in case the upgrade got interrupted.
I mounted an older kernel. What I found was very odd. Many of the kernel module files for the kernel that was being installed when the system turned off were 0 sized! This makes no sense as there are many GB free on the partition. So I had to install the latest Tumbleweed kernel packages via rpm. After that, the boot and WiFi works as expected. I had also lost the Broadcom WiFi in the recovery kernel. But that is working as well. Anyway, all seems okay now. Except snapper is not configured. I need to find exactly how yast would have set up snapper in the original install, and then do the same. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 22/01/18 08:38, Roger Oberholtzer wrote:
I mounted an older kernel. What I found was very odd. Many of the kernel module files for the kernel that was being installed when the system turned off were 0 sized! This makes no sense as there are many GB free on the partition. So I had to install the latest Tumbleweed kernel packages via rpm. After that, the boot and WiFi works as expected. I had also lost the Broadcom WiFi in the recovery kernel. But that is working as well.
This is a well-known failure mode for many file-systems - not just btrfs. It's the usual race condition - not help by the file-system devs' desire to protect the file system and directory structure at the expense of user data ... What has presumably happened is that the kernel and everything was created, and just as it was all being flushed to disk, the system went belly-up. All the meta-data (directory entries etc) had made it to the journal, so when the system came back, the journal ran, and all the files appeared. BUT THE DATA. That was NOT journalled, so when the files themselves appeared, there was nothing to put in them ... :-( Cheers, Wol -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Jan 22, 2018 at 4:37 PM, Wols Lists <antlists@youngman.org.uk> wrote:
BUT THE DATA. That was NOT journalled, so when the files themselves appeared, there was nothing to put in them ... :-(
I do wonder what other files may have been effected. Perhaps I need to do an rpm verify to see what does not match. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The openSUSE tutorial for snapper is here: https://en.opensuse.org/openSUSE:Snapper_Tutorial What it seems to lack is telling how the openSUSE install sets up snapper. As my system did not do this during install, I need to so so by hand. It would be nice to set it up exactly as the OS install would have. Otherwise I may have a setup that does not work as expected with zypper and such. Is this documented anywhere? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
The openSUSE tutorial for snapper is here:
https://en.opensuse.org/openSUSE:Snapper_Tutorial
What it seems to lack is telling how the openSUSE install sets up snapper. As my system did not do this during install, I need to so so by hand. It would be nice to set it up exactly as the OS install would have. Otherwise I may have a setup that does not work as expected with zypper and such.
Is this documented anywhere?
Richard had posted a link to the new way lately, https://rootco.de/2018-01-19-opensuse-btrfs-subvolumes/ but likely you rather have the old setup with many var subvolumes... (my own setup error so snapper wouldn't work properly was 'only' a separate /boot directory - maybe that's your problem, too?) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jan 24, 2018 at 1:42 PM, Peter Suetterlin <pit@astro.su.se> wrote:
Richard had posted a link to the new way lately, https://rootco.de/2018-01-19-opensuse-btrfs-subvolumes/ but likely you rather have the old setup with many var subvolumes...
I have the older Tumbleweed setup from some time in the summer. I do not need to sort out the btrfs volumes. I think they are all present. It is just enabling snapper as the openSUSE install should have done that I need to do. Currently, snapper list-configs lists nothing. Is this all that is needed? snapper -c root create-config / -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
I have the older Tumbleweed setup from some time in the summer.
I do not need to sort out the btrfs volumes. I think they are all present. It is just enabling snapper as the openSUSE install should have done that I need to do.
Yeah, figured that out - just too late :o
Currently, snapper list-configs lists nothing.
Is this all that is needed?
snapper -c root create-config /
I *think* so. Check that grub2-snapper-plugin and snapper-zypp-plugin are installed (maybe also yast2-snapper), and check status of snapper-cleanup.timer and snapper-timeline.timer. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
24.01.2018 16:38, Peter Suetterlin пишет:
Roger Oberholtzer wrote:
I have the older Tumbleweed setup from some time in the summer.
I do not need to sort out the btrfs volumes. I think they are all present. It is just enabling snapper as the openSUSE install should have done that I need to do.
Yeah, figured that out - just too late :o
Currently, snapper list-configs lists nothing.
Is this all that is needed?
snapper -c root create-config /
I *think* so.
Check that grub2-snapper-plugin and snapper-zypp-plugin are installed (maybe also yast2-snapper), and check status of snapper-cleanup.timer and snapper-timeline.timer.
To enable rollback with snapper it is necessary 1. Your root subvolume should be one of snapper snapshots 2. default-subvolume should be set to your root subvolume 3. SUSE_BTRFS_SNAPSHOT_BOOTING="true" should be set in /etc/default/grub 4. grub2 should be reinstalled with new setting (really reinstalled, not just configuration) - "update-bootloader --reinit" This is in addition to normal configuration like having @/.snapshots subvolume that is mounted as /.snapshots. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Jan 24, 2018 at 6:05 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
To enable rollback with snapper it is necessary
Thanks for that info. It gives me something to look at. Except I'm not certain what is meant by #1 and #2. How do I verify this? Or would these be the case when the disk was set up by the openSUSE Tumbleweed install?
1. Your root subvolume should be one of snapper snapshots 2. default-subvolume should be set to your root subvolume 3. SUSE_BTRFS_SNAPSHOT_BOOTING="true" should be set in /etc/default/grub 4. grub2 should be reinstalled with new setting (really reinstalled, not just configuration) - "update-bootloader --reinit"
This is in addition to normal configuration like having @/.snapshots subvolume that is mounted as /.snapshots.
I see this from mount on a system with snapper set up: /dev/sda2 on / type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot) /dev/sda2 on /.snapshots type btrfs (rw,relatime,space_cache,subvolid=258,subvol=/@/.snapshots) So I should see the pretty much same on my mystery machine, I guess? (It's at home, and I'm not there right now...) -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
25.01.2018 11:24, Roger Oberholtzer пишет:
On Wed, Jan 24, 2018 at 6:05 PM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
To enable rollback with snapper it is necessary
Thanks for that info. It gives me something to look at. Except I'm not certain what is meant by #1 and #2. How do I verify this? Or would
Well, looking at /proc/self/mountinfo for "/" mount and subvol= option as well as checking "btrfs subvolume get-default /".
these be the case when the disk was set up by the openSUSE Tumbleweed install?
Yes if snapshots were enabled during installation.
1. Your root subvolume should be one of snapper snapshots 2. default-subvolume should be set to your root subvolume 3. SUSE_BTRFS_SNAPSHOT_BOOTING="true" should be set in /etc/default/grub 4. grub2 should be reinstalled with new setting (really reinstalled, not just configuration) - "update-bootloader --reinit"
This is in addition to normal configuration like having @/.snapshots subvolume that is mounted as /.snapshots.
I see this from mount on a system with snapper set up:
/dev/sda2 on / type btrfs (rw,relatime,space_cache,subvolid=259,subvol=/@/.snapshots/1/snapshot) /dev/sda2 on /.snapshots type btrfs
Yes, but /.snapshots/1 should also be valid snapper snapshot, i.e. "snapper list" should show you snapshot #1.
(rw,relatime,space_cache,subvolid=258,subvol=/@/.snapshots)
So I should see the pretty much same on my mystery machine, I guess? (It's at home, and I'm not there right now...)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Oliver Kurz -
Peter Suetterlin -
Roger Oberholtzer -
Wols Lists