<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/05/2014 09:50 AM, Josef Bacik
wrote:<br>
</div>
<blockquote
cite="mid:CAEzrpqf9CvmkdQA2xqpbhaYdCJJ2R=ccz=tP+CRqpFk+zCohLA@mail.gmail.com"
type="cite">
<p dir="ltr">On Oct 2, 2014 11:32 PM, "Andre Robatino" <<a
moz-do-not-send="true"
href="mailto:robatino@fedoraproject.org">robatino@fedoraproject.org</a>>
wrote:<br>
><br>
> openSUSE 13.2, scheduled for release in November, will have
btrfs as the<br>
> default filesystem. What are the chances that F22 will
follow suit, assuming<br>
> openSUSE has no major problems with it?<br>
><br>
> <a moz-do-not-send="true"
href="https://news.opensuse.org/2014/09/22/">https://news.opensuse.org/2014/09/22/</a><br>
></p>
<p dir="ltr">My plan is to push for F23, I'm still wrapping up
some balance bugs and some other issues we've found at work and
then this will be my next priority. Suse benefits from having a
narrow "supported" criteria, like only use it with lots of space
and don't use any of the RAID stuff, plus they have two kernel
guys on it and Dave Sterba who is now in charge of btrfs-progs.
Fedora unfortunately has me who has Facebook work to do and Eric
who is a professional fs juggler. We will get there, and when we
do it will be less painful than its going to be for Suse since
they will have fixed it all for us ;). Thanks,</p>
<br>
</blockquote>
F23 sounds about right to me. I am very much a fan of BTRFS and
currently use it on all of my systems with few problems but I think
that F22 is a bit early to make it the default.<br>
<br>
However, I do believe that there a couple of things that need to
happen to make thjings easier/better:<br>
<br>
1. The Fedora developers/maintainers need to take BTRFS more
seriously and address btrfs related problems seriously and quickly.
Yes, I know that BTRFS swap draining is a little bit difficult to
deal with when you are up to you rear end in alligators but, a
little more attension please.<br>
<br>
2. Currently anaconda supports supports installation of /boot on
BTRFS either as a simple directory on a BTRFS volume (yes, I don't
understand why someone would do this but ...), as a simple directory
on a rootfs ("/") subvolume, or as a spepate subvolume. Grub2.02
also supports this and grubby will support if "real soon now" when
pjones can get enough time to examine and integrate my grubby
patches adding BTRFS support.<br>
<br>
3. About the only thing that I would like to see changed is to move
the drop-down menu which selects the filesystem type from the
"custom" to the previous (disks?) panel. This would allow a user to
select BTRFS and then let anaconda do its automagic allocation.
Yes, I now it is not that hard to select custom, then select BTRFS
and then click on the auto allocation.<br>
<br>
Anyway, we are getting close.<br>
<br>
Gene<br>
<br>
</body>
</html>