Re: Scoping out the change needed for Anaconda to support resizing Btrfs filesystems

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


On Fri, Nov 13, 2020 at 2:22 PM <jkonecny@xxxxxxxxxx> wrote:
> Hello Michel,
> It's great to see community help for the BTRFS features! We will try to
> help you to get the work done as smooth as possible.
> First advice. If you need help with debbuging or questions about code
> just come to our #anaconda on freenode IRC and you should be able to
> get answers soon (GMT +1, Czech Republic timezone).
> For the rest see my replies below.
> On Thu, 2020-11-12 at 17:11 -0800, Michel Alexandre Salim wrote:
> > Dear Anaconda developers,
> >
> > There's this 7 year old bug about Anaconda not being able to resize
> > Btrfs filesystems, despite Btrfs itself supporting resizing.
> >
> >
> >
> > Now that Fedora defaults to Btrfs on desktop variants, since Facebook
> > uses Fedora as its preferred desktop Linux distribution we might be
> > able to dedicate some manpower to working on this, but need help to
> > scope out this work.
> >
> > Would any change needed be limited to python-blivet, or would other
> > components need to be touched?
> I didn't looked on the code but I expect that you have to take care of
> both blivet and Anaconda to fix the RFC.


this change should affect only the "Reclaim Disk Space" dialog. Is it
correct? In that case, its scope depends on the Blivet's
implementation. If the btrfs partition can be resizable the same way
as any other resizable partition, no changes should be needed in
Anaconda. Otherwise, it might be necessary to modify our
implementation, extend the DBus API or change the user interface.

I'm adding Vojta Trefny to CC.


> >
> > Also, what's the best way to test this, build Anaconda from the
> > master
> > branch and use it for our installation?
> Building is too unpleasant experience for testing. Ideally you should
> be using updates image feature[1]. Updates image is just an image (or
> tar) which is upacked and files in it will replace files in the
> installation environment. Until you need to touch Dracut code (not
> expected here) you should be fine to generate updates image, upload to
> a HTTP server and boot with inst.updates. You can also replace blivet
> by this. See my blog post about Anaconda debugging for more details[2].
> My recommended way is to use the make-updates wrapper[3] mentioned as
> the last part in blog post. Also for any other questions please feel
> free to ask :).
> Aside of this. This is a great candidate for Pure Community Feature[4].
> If possible, could you or someone else please maintain this feature in
> Anaconda so there will be contact on someone who can fix the feature if
> it breaks?
> [1]:
> [2]:
> [3]:
> [4]:
> Best Regards,
> Jirka
> _______________________________________________
> Anaconda-devel-list mailing list
> Anaconda-devel-list@xxxxxxxxxx

Anaconda-devel-list mailing list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux