On 2024-03-18 13:49, Roger Oberholtzer wrote:
> On Mon, Mar 18, 2024 at 1:31 PM Darryl Gregorash <raven@accesscomm.ca <>> wrote:
> On 2024-03-18 03:39, Roger Oberholtzer wrote:
> I booted from the main menu. I did not navigate anywhere like to
> Read-only snapshots. So I would have expected it to be writable as well.
> Odd that the system has gotten into a state where there are no writable
> options. snapper rollback just says:
>
> Ambit is transactional.
> Active snapshot is already default snapshot.
>
> Sigh. I don't want to do a reinstall. All the software is set exactly as
> I want. It's one of (not the only) systems on which I develop software.
> Oh well. Time to extract all the needed information from it!
Andrei made a suggestion.
I think I have tried all the suggestions. The filesystem seems implacable. Everything is there and, as far as I can tell in a ro root filesystem, all seems to be working great. Sooo close. And yet soooo far.
> I still cannot believe that snapper cannot do whatever it does to allow
> changes. A new snapshot. Couldn't I make a snapshot via some other
> command than rollback? Or is it that since I'm in a snapshot, there is
> nothing to make a snapshot of and then allow new changes after that. If
> I wasn't booted into it perhaps? Like boot from a USB stick and then try
> the rollback on this filesystem? I suspect I'm just demonstrating my
> ignorance about that it the reason for the problem.
You are just demonstrating one of my reasons for not using btrfs :-)
I have never had an issue before. I am sure that my rollback when I mistakenly thought that a zypper dup had mysteriously restarted the system and things looked very wrong are the cause of all this. I was hasty.
--
Cheers / Saludos,
Carlos E. R.
(from 15.5 x86_64 at Telcontar)