growfs for hammer?

[Sascha Wildner]

On Wed, 04 Mar 2015 08:29:47 +0100, Remi Locherer <remi.locherer at relo.ch>  
wrote:

> Hi,
>
> I installed dragonfly on a server with a 2TB raid volume. The installer
> just used 500GB out of the 2TB. I could grow the slice and partition
> with fdisk and disklabel64. How can I grow hammer?

You can't.

> hurricane# fdisk da0
> ******* Working on device /dev/da0 *******
> parameters extracted from device are:
> cylinders=242244 heads=256 sectors/track=63 (16128 blks/cyl)
>
> Figures below won't work with BIOS for partitions not in cyl 1
> parameters to be used for BIOS calculations are:
> cylinders=242244 heads=256 sectors/track=63 (16128 blks/cyl)
>
> Media sector size is 512
> Warning: BIOS sector numbering starts with sector 1
> Information from DOS bootblock is:
> The data for partition 1 is:
> sysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
>     start 63, size 3906911169 (1907671 Meg), flag 80 (active)
>         beg: cyl 0/ head 1/ sector 1;
>         end: cyl 1023/ head 255/ sector 63

Looks OK, 2TB here.

> # /dev/da0s1:
> #
> # Informational fields calculated from the above
> # All byte equivalent offsets must be aligned
> #
> # boot space:    1044992 bytes
> # data space: 1953454555 blocks # 1907670.46 MB (2000337464832 bytes)

2TB here too.

> 16 partitions:
> #          size     offset    fstype   fsuuid
>   a:    1048576          0    4.2BSD    #    1024.000MB
>   b: 1952404952    1048576    HAMMER    # 1906645.461MB
>   a-stor_uuid: f3b48ee3-9b47-11e4-ab34-012481a71e2c
>   b-stor_uuid: f3b48f25-9b47-11e4-ab34-012481a71e2c

This looks weird, it is showing a 1GB /boot and the rest seems to be  
assigned to the 'b' partition. Did you remove or mess with swap in the  
installer's partition configuration screen?

Sascha