* Niklas Haas <lists.suse@haasn.dev> [06-01-21 18:11]:
This change completely broke my system as well.
(1445/7248) Installing: filesystem-15.5-40.2.x86_64 ...................[error] Installation of filesystem-15.5-40.2.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Make a copy of `/bin'. Merge the copy with `/usr/bin'. Clean up duplicates in `/usr/bin'. Make a copy of `/sbin'. Merge the copy with `/usr/sbin'. Clean up duplicates in `/usr/sbin'. Make a copy of `/lib'. Merge the copy with `/usr/lib'. Clean up duplicates in `/usr/lib'. Make a copy of `/lib64'. Merge the copy with `/usr/lib64'. Clean up duplicates in `/usr/lib64'. Switch to new `/usr/bin'. renameat2: Invalid argument Something failed, cleaning up error: lua script failed: [string "%pretrans(filesystem-15.5-40.2.x86_64)"]:37: exit error: filesystem-15.5-40.2.x86_64: install skipped error: filesystem-15.5-40.1.x86_64: erase skipped
Abort, retry, ignore? [a/r/i] (a):
I chose `retry`, which resulted in exactly the same output, followed by `abort`. After this, my system was unusable. Basic commands such as `/bin/ls` etc. did not work.
Luckily, I have zypper configured to make a zfs snapshot immediately prior to any operation, so recovery was as simple as booting into a dracut rescue shell and running `zfs rollback`. (An aside: Apparently the `bootfs.rollback` parameter does not work, I had to do it manually from a shell.)
I think that, quite frankly, such dangerous upgrades that have a high potential for total system destruction need to be communicated to users in a much more visible manner than some obscure mailing list nobody follows. Something like Gentoo's `eselect news` system would be a much better mechanism to communicate breaking changes well in advance. Let's be honest, nobody checks these mailing lists until *after* their system is a brick.
That aside, does anybody know what could be going on? The `renameat2: Invalid argument` command seems like the most obvious suspect. Is it possible that it's requiring some flag that zfs may or may not implement? Is there any work-around, or a way to perform this change manually? (The wiki does not really go into detail here, except elaborating on the existence of a magical-script-that-solves-everything. I would suggest adding some sort of step-by-step instruction for what this script is actually doing, so we can do it by hand, on systems affected by this bug.)
I too had problems and have rebooted to kernel 5.12.4-1-default. My nvidia G04 doesn't give me a full screen. Reinstalled the 4 nvidia packages, nvidia-computeG04 390.143-44.2 nvidia-gfxG04-kmp-default 390.143_k5.12.4_9-44.23 nvidia-glG04 390.143-44.2 x11-video-nvidiaG04 390.143-44.2 didn't help, reverted to 5.12.4-1-default kernel and most appears well. but I had no errors on the zypper dup -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode