Re: Bug#652275: Guided partitioning should not offer separate /usr, /var, and /tmp partitions; leave that to manual partitioning

[Goswin von Brederlow <goswin-v-b@web.de>]

Josh Triplett <josh@joshtriplett.org> writes:

> On Sun, Dec 18, 2011 at 06:48:53PM +0100, Goswin von Brederlow wrote:
>> Josh Triplett <josh@joshtriplett.org> writes:
>> > spools (/var/spool/mail), large websites in the default location
>> > (/var/www), or large databases (/var/lib/postgresql or similar) will
>> > need a lot more.  The same applies in reverse, when /var has space to
>> > spare but other partitions don't.  And even experienced sysadmins find
>> > it painful to either resize disk partitions or create magic bind mounts
>> > to partitions that have space.
>> 
>> lvresize, resize2fs, done
>
> Doesn't make it any less painful.  (Also, don't forget the resize2fs and
> lvresize of some other partition first, and figuring out the appropriate
> amount of space to move around.)  This also assumes LVM, which we don't
> default to.

As I said the initial partitions should be small with free space left
over to grow them as needed. Most filesystems don't support shrinking,
not even offline so leaving free space is the only way to go.

And I think multiple partitions without lvm makes no sense as non custom
setup. Resizing is likely to be required at some point and basically
impossible with real partitions.

MfG
        Goswin

PS: Lvm1 had a tool to resize the LV and FS with one command. I miss
that for lvm2.