[SOLVED] Filesystemsize

andreashuemmer

Hi folks,

using a 250 GB drive, the setup obviously uses only 20GB and leaves 230GB unpartitioned free space. Is the by intent or is this ab bug?
Can it be extended without any hazzle or are the things to consider?

mwilliams

What deployment type did you use? ISO/OVA/PI?

andreashuemmer

Installed it via ISO (latest)

noplan

cannot confirm this installed with iso on bare metal
conclusio entire HDD is used

mwilliams

As @noplan writes: We can't reproduce this. Assumption is that the disk was created with the 20GB and then extended later.

Extending within the appliance is quite simple:

adapt the partition table to larger disk
in very short: fdisk -> delete partition -> re-create with identical start cylinder -> new sector count
btrfs filesystem resize max /

Here you have more detail: https://www.suse.com/support/kb/doc/?id=000018798

WalterH

Having 230 GB of unpartitioned space is an advantage. You should move /var/lib/gromox/ to its own volume and the 230 GB are optimal for this. Do not forget the symlink or mount it to /var/lib/gromox/.
/var/lib/gromox/ contains the data.

crpb

Und für die VMWare-Front im laufenden Betrieb vergrößern....

cb@asterix:pts/7->/home/cb (0) 
> pwsh
PS /home/cb> $myvcenter = Connect-VIServer -Server vcenter-hostname
PS /home/cb> Get-VM -Name 'grommunio_appl*'|Get-HardDisk |Set-HardDisk -SizeGB 40
PS /home/cb> exit
cb@asterix:pts/18->/home/cb (0) 
> ssh grommunio-host
root@gromi [~]: $ 
> zypper ref && zypper in growpart
> echo 1 > /sys/block/sda/device/rescan
> growpart /dev/sda 3
> btrfs filesystem resize max /

Zwischen drin halt bestätigen und so...
;-)

growpart

itNGO

crpb Geht auch unter Proxmox oder HyperV so....

crpb

itNGO

Und unter Xen und KVM auch :p.
Also der Rescan und Growpart teil natürlich.