Adding partition

[Glenn Dawson]

At 12:27 PM 3/13/2006, Jerry McAllister wrote:
> >
> > Good Day,
> >
> > There is free space at the end of my disk and I want to move
> > /usr/ports do a dedicated partition.
> >
> > # disklabel /dev/ad10s1
> > # /dev/ad10s1:
> > 8 partitions:
> > #        size   offset    fstype   [fsize bsize bps/cpg]
> >    a:  1024000        0    4.2BSD     2048 16384 64008
> >    b:  2252800 44032000      swap
> >    c: 368627427        0    unused        0     0   # "raw"
> >    d:  2048000  1024000    4.2BSD     2048 16384 28552
> >    e: 20480000  3072000    4.2BSD     2048 16384 28552
> >    f: 20480000 23552000    4.2BSD     2048 16384 28552
> >
> > I want to add a g partition with 10 GByte to end.
> >
> > When I enter "disklabel -e /dev/ad10s1" vi opens and I add
> > the following line to the end:
> >
> >    g: 20480000 44032000    4.2BSD     2048 16384 28552
> >
> > Upon saving I get an error that partitions "c" and "g" overlap.
> > As far as I have read this is on purpose. How can I avoid the
> > error message?
>
>I don't know why it would say that c and g overlap, but you have
>forgot to include the space used for swap in the offset.
>Your offset should really be 46284800.
>
>I have heard that some people think you should put your swap at the
>highest address, but I don't think that applies in any significant
>way to modern drives.    I could be wrong on that, though.

On some current drives, I've seen differences in sustained throughput 
of up to 2 to 1 when comparing the beginning of the disk and the end 
of the disk.  The beginning of the disk being faster.

-Glenn

>Anyway, using the partition labels out of order does lead to confusion
>and errors in calculations - in my experience.
>
>By the way, did you notice that you can use '*' in the offset field and
>bsdlabel (or disklabel since 4.xx) will calculate it for you.   You can
>even put a '*' in the last partition (highest address) size AND offset
>fields and bsdlabel will calculate it for you.
>
>I also wonder at your keeping such a large chunk of the FreeBSD slice
>unallocated that way.   Now, if you had reduced the slice, I would think
>you were saving it for another OS.   But it is already in FreeBSD space
>so just put it all in g:   But, to each their own.
>
>////jerry
>
> >
> > I tried it via sysinstall but didn't work either. When saving
> > the new disklabels I get "Unable to write data to disk ad10".
> > I assume that is because ad10 is currently mounted?
> >
> > Thank you!
> >
> > Markus
> >
> >
> > _______________________________________________
> > freebsd-questions at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe at freebsd.org"
> >
>
>_______________________________________________
>freebsd-questions at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"