Idea floated on #fedora-workstation is to have a weekly status report by email. The idea is to make sure that everyone is kept in the loop, while at the same time making sure Btrfs isn't bumping other priorities off the meeting agenda.
- What has and hasn't happened since the last update: what has made progress, what might be stalled. - Any particularly nasty bug reports - Urgent priority questions/concerns about these reports should be brought up in the "Follow-ups & Status reports" portion of weekly WG meetings - Any normal questions/concerns/requests for more details should be brought up in Open Floor, or respond to the report email
-------
(This first update is big. Subsequent updates should be smaller.)
Changes:
+ Anaconda defaults to Btrfs for automatic partitioning for all desktop installation media
+ libvirtd patches have landed that will set 'nodatacow' (chattr +C) on VM image containing directories when on Btrfs, by default: virt-manager, GNOME Boxes, Cockpit, et al, will benefit from this directly; minimally tested OK, needs some further testing
+ Numerous btrfs kernel patches, related to Fedora concerns and requests have landed on upstream linux-btrfs@, including new 'rescue=all' mount option to better tolerate read-only mount despite file system damage
+ anaconda fix for Silverblue on Btrfs, set "rootflags" boot parameter so startup succeeds
+ various compose related fixes for non-ISO images; PR submitted, not yet merged into production (consequence is, these Rawhide images are not being created right now for armhfp: Workstation, KDE, Xfce, LXDE, MATE, Sugar)
+ btrfs driver is now built-in to the kernel, rather than as a module
+ Red Hat CKI (Continuous Kernel Integration) have added btrfs to their regular xfstests and will report failures upstream
Communication:
+ Fedora Magazine article(s) are in the idea and specification phase. https://pagure.io/fedora-workstation/issue/162 https://discussion.fedoraproject.org/t/btrfs-by-default/22020 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/216?kanb...
Documentation:
+ Draft material available for review, organization and content development in-progress. https://pagure.io/fedora-workstation/issue/158
+ Clarification on what degree effort should be spent on updating upstream wiki so it doesn't conflict with Fedora reality; versus Fedora specific content focus.
Noteworthy bugs:
+ Btrfs corruption tracked down to bad RAM (confirmed with memtest86+); will result in improvements to 'btrfs check --repair' to better handle this case; does also expose the difficulty with Btrfs only stating the facts rather than pointing the finger at the cause. https://bugzilla.redhat.com/show_bug.cgi?id=1857996
+ Btrfs tracking bug https://bugzilla.redhat.com/show_bug.cgi?id=1851166
-- Chris Murphy
Hi Chris,
This is interesting, can you send them to devel@ too given that the feature is wider than just Workstation.
Peter
On Sun, Jul 26, 2020 at 11:30 PM Chris Murphy lists@colorremedies.com wrote:
Idea floated on #fedora-workstation is to have a weekly status report by email. The idea is to make sure that everyone is kept in the loop, while at the same time making sure Btrfs isn't bumping other priorities off the meeting agenda.
- What has and hasn't happened since the last update: what has made
progress, what might be stalled.
- Any particularly nasty bug reports
- Urgent priority questions/concerns about these reports should be
brought up in the "Follow-ups & Status reports" portion of weekly WG meetings
- Any normal questions/concerns/requests for more details should be
brought up in Open Floor, or respond to the report email
(This first update is big. Subsequent updates should be smaller.)
Changes:
- Anaconda defaults to Btrfs for automatic partitioning for all
desktop installation media
- libvirtd patches have landed that will set 'nodatacow' (chattr +C)
on VM image containing directories when on Btrfs, by default: virt-manager, GNOME Boxes, Cockpit, et al, will benefit from this directly; minimally tested OK, needs some further testing
- Numerous btrfs kernel patches, related to Fedora concerns and
requests have landed on upstream linux-btrfs@, including new 'rescue=all' mount option to better tolerate read-only mount despite file system damage
- anaconda fix for Silverblue on Btrfs, set "rootflags" boot parameter
so startup succeeds
- various compose related fixes for non-ISO images; PR submitted, not
yet merged into production (consequence is, these Rawhide images are not being created right now for armhfp: Workstation, KDE, Xfce, LXDE, MATE, Sugar)
btrfs driver is now built-in to the kernel, rather than as a module
Red Hat CKI (Continuous Kernel Integration) have added btrfs to
their regular xfstests and will report failures upstream
Communication:
- Fedora Magazine article(s) are in the idea and specification phase.
https://pagure.io/fedora-workstation/issue/162 https://discussion.fedoraproject.org/t/btrfs-by-default/22020 https://teams.fedoraproject.org/project/asamalik-fedora-magazine/us/216?kanb...
Documentation:
- Draft material available for review, organization and content
development in-progress. https://pagure.io/fedora-workstation/issue/158
- Clarification on what degree effort should be spent on updating
upstream wiki so it doesn't conflict with Fedora reality; versus Fedora specific content focus.
Noteworthy bugs:
- Btrfs corruption tracked down to bad RAM (confirmed with
memtest86+); will result in improvements to 'btrfs check --repair' to better handle this case; does also expose the difficulty with Btrfs only stating the facts rather than pointing the finger at the cause. https://bugzilla.redhat.com/show_bug.cgi?id=1857996
- Btrfs tracking bug
https://bugzilla.redhat.com/show_bug.cgi?id=1851166
-- Chris Murphy _______________________________________________ desktop mailing list -- desktop@lists.fedoraproject.org To unsubscribe send an email to desktop-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.or...
On Mon, Jul 27, 2020 at 1:15 AM Peter Robinson pbrobinson@gmail.com wrote:
Hi Chris,
This is interesting, can you send them to devel@ too given that the feature is wider than just Workstation.
Yes, good point. I'll cross post in the future.
On Sun, Jul 26, 2020 at 4:29 PM Chris Murphy lists@colorremedies.com wrote:
Documentation:
- Draft material available for review, organization and content
development in-progress. https://pagure.io/fedora-workstation/issue/158
- Clarification on what degree effort should be spent on updating
upstream wiki so it doesn't conflict with Fedora reality; versus Fedora specific content focus.
+ Clarification is needed to what degree effort should be spent on updating
The post to devel@ has this modification.
desktop@lists.stg.fedoraproject.org
-
Chris Murphy -
Peter Robinson