Re: 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]

 



On Sun, May 12, 2019 at 01:09:40PM +0200, Rolf Fokkens wrote:
> 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.
> 

  This is huge!  Accidentaly, after upgrade to F30 I experience
two or three I/O hangs with bcache, so I temporarily detached cache
device and (knock on wood) there are no problems (my rootfs is btrfs
raid10 over bcache devices).

  I suggest:
  1) getting this bug into F30 Common Bugs page, with hint that
  detaching cache device before upgrade could help.
  2) complement rhbz#1708315 with pointers to upstream report.


-- 
Tomasz Torcz            There exists no separation between gods and men:
xmpp: zdzichubg@xxxxxxxxx   one blends softly casual into the other.
_______________________________________________
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