Resize Root partition

SUSE Linux Enterprise Server SLES Configure-Administer
1

I have a Suse Enterprise Server 12 installed on a VMware server, I want to be able to increase the root volume, ideal I would like to be able to set it to auto expand. below is the layout.

df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/system-root 10G 8.4G 1.1G 89% /

udev 916M 100K 916M 1% /dev

tmpfs 916M 112K 916M 1% /dev/shm

/dev/sda1 61M 43M 15M 75% /boot

Disk /dev/sdb: 16.1 GB, 16111501312 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 128 25174143 12587008 8e Linux LVM

Disk /dev/sda: 171 MB, 171835392 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 128 128639 64256 83 Linux

Disk /dev/mapper/system-root: 10.7 GB, 10737418240 bytes

Disk /dev/mapper/system-root doesn’t contain a valid partition table

Disk /dev/mapper/system-swap: 2147 MB, 2147483648 bytes

Disk /dev/mapper/system-swap doesn’t contain a valid partition table

2

Hi jbrines,

[QUOTE=jbrines;21901]I have a Suse Enterprise Server 12 installed on a VMware server, I want to be able to increase the root volume, ideal I would like to be able to set it to auto expand. below is the layout.

df -h

Filesystem Size Used Avail Use% Mounted on

/dev/mapper/system-root 10G 8.4G 1.1G 89% /

udev 916M 100K 916M 1% /dev

tmpfs 916M 112K 916M 1% /dev/shm

/dev/sda1 61M 43M 15M 75% /boot

Disk /dev/sdb: 16.1 GB, 16111501312 bytes

Device Boot Start End Blocks Id System

/dev/sdb1 128 25174143 12587008 8e Linux LVM

Disk /dev/sda: 171 MB, 171835392 bytes

Device Boot Start End Blocks Id System
/dev/sda1 * 128 128639 64256 83 Linux

Disk /dev/mapper/system-root: 10.7 GB, 10737418240 bytes

Disk /dev/mapper/system-root doesn’t contain a valid partition table

Disk /dev/mapper/system-swap: 2147 MB, 2147483648 bytes

Disk /dev/mapper/system-swap doesn’t contain a valid partition table[/QUOTE]

first of all, I strongly recommend to further split your file systems - at least deparate /tmp/, /var, /var/log and then those parts that could “eat up” disk space on their own. You wouldn’t want to have your root FS (or /var) getting full just because some user/process puts a lot of stuff in /tmp, in some run-time file below /var or by creating bazillion syslog messages per second.

While I haven’t toyed with SLES12 yet, I’m certain you can (manually) expand file systems live, either via YaST or via command line tools (lvresize + FS resize). All you need is sufficient free extends in the VG, which you could make available any time by adding more virtual disks to your VM and adding them as PVs to the volume group.

I’m not aware of any ready-to-run automation for volume resizing, but of course nothing keeps you from adding according actions to your system monitoring scripts :wink:

Regards,
Jens

3

[QUOTE=jmozdzen;21902]Hi jbrines,

first of all, I strongly recommend to further split your file systems - at least deparate /tmp/, /var, /var/log and then those parts that could “eat up” disk space on their own. You wouldn’t want to have your root FS (or /var) getting full just because some user/process puts a lot of stuff in /tmp, in some run-time file below /var or by creating bazillion syslog messages per second.

While I haven’t toyed with SLES12 yet, I’m certain you can (manually) expand file systems live, either via YaST or via command line tools (lvresize + FS resize). All you need is sufficient free extends in the VG, which you could make available any time by adding more virtual disks to your VM and adding them as PVs to the volume group.

I’m not aware of any ready-to-run automation for volume resizing, but of course nothing keeps you from adding according actions to your system monitoring scripts :wink:

Regards,
Jens[/QUOTE]

Hi Jens,

Cheers for the info.

Can you use Yast to increase the root partition?

John.

4

Hi John,

Can you use Yast to increase the root partition?

Technically speaking, there’s no difference between any “currently active” file system while the system is up - I don’t see a reason when this shouldn’t be possible. On the other hand, SLES12 (which you’ve been naming in your initial post) isn’t publicly available (AFAIK), so your mileage may vary and things may change until the final version is shipped.

Regards,
Jens

5

Hi John,

sorry, I forgot a side note: You haven’t mentioned what file system you’re running: Of course your FS needs to support live resizing (i.e ext3/4 does support this). But that should be simple to find out - do a single test run :wink:

Regards,
Jens