Upgrade to Fedora 30 consistently corrupts bcache storage - is there some kind of emergency brake possible during upgrade?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi All,

There's this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1708315

Would have been better if I discovered it during Alpha or Beta, but unfortunately I didn't. Now we have the situation that any bcache user upgrading to Fedora30 involuntarily currupts his storage.

I tried to limit the impact by using a %pretrans script in bcache-tools:

%pretrans
_bcache=`find /sys/block/ -maxdepth 1 -name "bcache[0-9]*" | wc -l`
[[ $_bcache -gt 0 ]] || exit 0
cat >&2 << EOF
bcache will likely corrupt Fedora 30 systems beyond repare.
https://bugzilla.redhat.com/show_bug.cgi?id=1708315
EOF
exit 1

But this only blocks upgrading/installing bcache-tools. The rest (including the kernel) is still upgraded so after a reboot the storage will get corrupted anyway. Of course adding this to the kernel package would do the trick, but I'm not sure if that is an option.

Any suggestions on how to save people from running into this are very welcome!

Cheers,

Rolf
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux