Re: Partitioning and the grow/max commands

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

 



Rebecca.R.Hepper@xxxxxxxxxxx wrote:


> zerombr yes
> clearpart --all
> part /boot --size 16
> part swap --size 512
> part / --size 250
> part /usr --size 1000 --grow --maxsize 2000
> part /var --size 1000 --grow --maxsize 2000
> part /usr/local --size 1000 --grow --maxsize 2000
> part /home --size 1000 --grow
> install
> 
> I was under the impression that remaining space would be divided 
> equallybetween the 3 partitions with the max 2000 command and then 
> the --grow
> command  would allocate all the remaining space to /home .  Yet if 
> you look
> at the results below of the df -h command, you will see that my 
> hard drives
> have unallocated space ( I didn't know how to see what the amount 
> of swap
> space is, but I only have it set at 512).  Did I do something wrong 
> or am I
> not understanding the grow and max commands incorrectly?  Thanks in
> advance!

Not sure what your question is, but I'll take a guess. Kickstart is not
using up the whole disk when you use just --grow with no maxsize? If ths
is the question, I've noticed that also. I haven't had time to find out
what the corelation of size or why it's happening, but a quick work
around is to add to --grow a --maxsize with an absurbly large number
that will always be larger than the disk. ie.:
part /home --size 1000 --grow --maxsize 999999999

Don't know what the largest --maxsize you could have, but I've used up
to 20000 with no problem.

hth

Steve





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux