Btrfs by default status updates, 2020-08-23

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

 



News:

+ A pagure project has been created "fedora-btrfs" for overall
development and planning for Btrfs in Fedora.
https://pagure.io/fedora-btrfs/project/

This is to consolidate high level Btrfs related issues, and planning
for future Fedora releases. It can include issues related to
documentation, article suggestions, feature requests, and integration.

Bugs should still be reported at bugzilla.redhat.com. Issues with
Btrfs user-space commands should be filed against the btrfs-progs
component. All other bugs should be filed against the kernel
component, while also setting the Assignee field to:
fedora-kernel-btrfs@xxxxxxxxxxxxxxxxx
-----

Changes:

+ Libvirt VMs set nodatacow for enclosing directory when on Btrfs - as
of libvirt-6.6.0

This is now in Fedora 33. The effect is the enclosing directories for
images have 'chattr +C' set. This affects Cockpit, GNOME Boxes, and
virt-manager. It will also work with virt-install using this syntax:

  virt-install --disk size=10

It won't get +C if using the explicit path:

  virt-install --disk size=10,path=/var/lib/libvirt/images/demo.img

Once chattr +C is set, anything created (new or copied) will inherit
this behavior. Anyone upgrading from Rawhide likely won't see this new
behavior, and may want to manually 'chattr +C' on the appropriate
enclosing directory. While you can't change an existing non-zero
length file to nodatacow, you can use 'cp' to duplicate it inside a
directory with nodatacow already set.


+ cp uses reflink=auto by default - as of coreutils-8.32-12.fc33
-----

Noteworthy bugs:

+ Creating an armhfp disk image with btrfs results in an empty filesystem
https://bugzilla.redhat.com/show_bug.cgi?id=1855034

The original reported bug was fixed a while ago; but since then
everything is copied to the Btrfs file system due to mount order
confusion. A big part of the difficulty is that problem doesn't
reproduce locally, only in Fedora compose system. A fix has been
pushed. Fingers crossed.
https://pagure.io/appliance-tools/pull-request/15


+ btrfs subvolume creation on a loop-mounted filesystem fails when
using qemu-user
https://pagure.io/fedora-btrfs/project/issue/11

This issue is exposed by the previously mentioned RHBZ. There seems to
be some confusion resulting from use in an emulated environment.
Debugging continues.
-----

Communication:

+ Fedora Magazine article "Btrfs Coming to Fedora 33" will be
published Monday, 24 August.
-----

Documentation:

+ A partial list of docs needing updates
https://pagure.io/fedora-workstation/issue/158#comment-672898
https://lists.fedoraproject.org/archives/list/docs@xxxxxxxxxxxxxxxxxxxxxxx/message/R5LKDK42VAIVSKC4NCLIMJCUKJRFGAO5/

Assistance in updating is appreciated, but in particular it'd be most
helpful to find additional weak spots that have not yet been
identified.



-- 
Chris Murphy
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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/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