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

Re: Proof of concept, early work in progress code for partition/filesystem resizing

On Wed, 2007-11-14 at 10:38 -0500, David Cantrell wrote:
> On Wed, 14 Nov 2007 09:47:46 -0500 Jeremy Katz <katzj redhat com> wrote:
> > I've been looking some at what we need to have to implement resizing of
> > partitions and filesystems within anaconda.  At this point, the code is
> > starting to work, although there are still some large-ish holes.  Also,
> > there are some functionality pieces that are entirely missing.  So to
> > start with the caveats:
> > 1) The UI is just enough to make it possible to test the code and not
> > the UI that we're going to actually want to use.  
> A question I just thought of is whether or not we want to support resizing via kickstart installs.  My guess is no because resizing is something that really needs to be more interactive than not, but maybe I'm wrong.
> I think we should come up with a policy on this earlier rather than later.

Oh yeah, I was thinking about this yesterday on the way home.  I think
that the right answer for resizing is "use %pre".  Maybe when we come up
with a better "language" to describe partitioning, we can integrate
I mean, I guess we could go for
  part / --size 2500 --resize --onpart sda1
without a clearpart and get to "working".  But I don't think it's as
clear and I'd rather not muddy those waters

> > 3) Only implemented for partitions.  Not RAID.  Not LVM.  I'm not sure
> > if we can do RAID.  LVM LVs are pretty easy.  LVM PVs look like they
> > have a lot more caveats based on looking at the pvresize man page
> I think LVM resize is doable, 

The thing that concerns me about VG/PV resizing is that the pvresize man
page says it won't do any block moving.  So if you're using extents
later in the disk, basically, you're screwed right now.  Which is kind
of sucky.

> but we should not even bother with RAID.  

I don't know that it makes sense either.  Realistically, the primary use
of this is "I want to install on my box that also has $OTHER_OS".  At
which point it's not interesting to resize the RAID.  

> Resizing RAID is sort of an oxymoron anyway.

mdadm does actually support it upon looking.  It's just a matter of
doing mdadm --grow.  But yeah, I think punting it for now is all kinds
of sane.


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