https://bugzilla.suse.com/show_bug.cgi?id=1222429 https://bugzilla.suse.com/show_bug.cgi?id=1222429#c6 Jiri Slaby <jslaby@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jslaby@suse.com) | --- Comment #6 from Jiri Slaby <jslaby@suse.com> --- (In reply to Wenruo Qu from comment #5)
Personally speaking, if you're going to use "rescue=" option, your fs is already screwed up on most cases.
Furthermore, most rescue= options would require ro mount option, and can not be remounted to RW, this is by design.
So I do not think we need "norecovery" mount option for btrfs at all.
I have no idea :). Talk to yast people in here...
Any more explanation on the "norecovery" mount option usage? Maybe I'm missing something critical.
So see also: (In reply to Ancor Gonzalez Sosa from comment #2)
For context, the usage of "norecovery" during upgrade was introduced here: https://github.com/yast/yast-update/pull/180 -- You are receiving this mail because: You are on the CC list for the bug.