Install problems for DragonFlyBSD 6.4.1

[Weitian LI]

On 5/1/25 1:41 AM, Nelson H. F. Beebe wrote:
> I have photographed various installer screens, and they all show that
> an 80GB or 160GB disk has been found, but the final filesystem seems
> stuck at 5GB or 6GB, depending on the filesystem type.
> 
> One of the installer screens that has shown up frequently is the one
> that says
> 
> 	WARNING: Small HAMMER filesystems can
> 	fill up very quickly!		
> 	...
> 
> I do not have a spare physical machine to try an installation there:
> VMs are my only possibility.
> 
> I've been running more than 30 DragonFlyBSD systems from version 3.6
> (November 2013) forward to 6.4.0 (January 2023) in virtual machines,
> and a home physical machine has been running version 5.8 stably for
> the last 5 years, so today's frustrations have been a surprise.
> 
> Does anyone have any idea why the full disk is inaccessible with all
> three filesystem types in DragonFlyBSD 6.4.1?
> 
> Has anyone seen similar experience with the new release?
> 
> Is there a "file extend" command that could expose the rest of the
> disk for use?

Sorry for the late reply.

It's supported to expand the slice, partition, and HAMMER2 filesystem.

For the MBR-based partition scheme, you could do something like:

# fdisk -x /dev/vbd0
# disklabel -xx /dev/vbd0s1

You can find more information about the -x option in fdisk(8), gpt(8) 
and disklabel(8) man pages.  See also the "growfs" subcommand in the 
hammer2(8) man page.


-- 
Weitian