http://bugzilla.opensuse.org/show_bug.cgi?id=1126900
http://bugzilla.opensuse.org/show_bug.cgi?id=1126900#c1
Ignaz Forster changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|Kubic |Bootloader
Assignee|iforster@suse.com |jsrain@suse.com
QA Contact|qa-bugs@suse.de |jsrain@suse.com
--- Comment #1 from Ignaz Forster ---
This is "just" a cosmetic problem when using health-checker on a read-only root
file system. The value will still be stored into the btrfs header as long as
'env_block' is set.
One possible solution I was thinking of would be to just ignore write errors to
/boot/grub/grubenv on btrfs.
Reasoning: For technical reasons on btrfs /boot/grub/grubenv is not the only
source to store the GRUB environment variables, they may also be stored as
btrfs meta data. When reading a value (with grub2-editenv or within GRUB
itself) these two sources will be merged to get the actual variable value.
As none of these sources is valid in itself anyway it doesn't matter whether
the data is visible in /boot/grub/grubenv. That's how it behaves nowadays
anyway, it's just that the error message wouldn't appear any more...
Does this sound reasonable?
--
You are receiving this mail because:
You are on the CC list for the bug.
