Based on the server type, you have multiple the solution to increase the cache size.
Backup your data
Before to extend the cache, copy all data of the cache into a secondary storage
Increase the disk volume capacity
RAID
- Add new disk(s) into the available RAID volume used as Nodeum Cache.
- Wait till the RAID reconstruction is finished (this can take couple of days depending of the disk size).
Virtual Machine Datastore
- Shutdown the Nodeum server
- Edit the Nodeum server setting, pick the correct disk and extent its size
- Save the configurations
Extend the volume partition
CAUTIONS
If the new disk partition will be greater than 16TB, the resize2fs command (version <1.43) will not work.
The error is : "resize2fs: New size too large to be expressed in 32 bits"
This can be fixed by using a latest version Gparted ; this tool will provide this command in 64bits version. A procedure to use Gparted is decribed below.
Gparted procedure :
Use a Live ISO and edit the disk size graphically :
- Download the Gparted ISO (https://gparted.org/download.php)
- Creation of an USB key with Gparted ISO (in following Gparted Live CD/USB creation procedure : https://gparted.org/livecd.php).
- Boot on the Live ISO
- For Physical Server, this can be done with a CD/USB key or via Remote Management Server interface (where ISO image will be mapped as a CD).
- For Virtual Server, you have to boot the VM on the downloaded Gparted ISO.
- When the server boot, you will get the Gparted graphical interface.
- If you have a disk partition higher than 16 TB, you need to have a 64 bits file system. To convert your file system into 64 bits, you need to execute this command with th Gparted terminal : sudo resize2fs -b /dev/sdb1
- Select the Nodeum cache disk (most of cases, /dev/sdb1), the 'resize/move' option should be available, click on it.
- Drag the vertical bar to extend the partition size
- Once done, click on Resize/Move
- Once done, click on apply to save the changes to the disk
- Once the resize have finished, reboot the server and enjoy your new bigger Cache.
Command line interface procedure (available starting Nodeum 1.8 and higher)
-
Stop all Nodeum services
[NODEUM:root]/usr/mtc/bin>./core_stop all
[core_stop] core_watchdog has stopped successfully (CORE_STOP/cstop_stop_watchdog).
[core_stop] Trying umount (CORE_STOP/cstop_stop_fuse).
[core_stop] Trying umount force (CORE_STOP/cstop_stop_fuse).
[core_stop] Trying umount lazy (CORE_STOP/cstop_stop_fuse).
umount: /mnt/FUSE: not mounted
[core_stop] core_fuse has stopped successfully (CORE_STOP/cstop_stop_fuse).
[core_stop] data_mining has stopped successfully (CORE_STOP/cstop_stop_data_mining).
[core_stop] core_manager has stopped successfully (CORE_STOP/cstop_stop_manager).
[core_stop] library_manager has stopped successfully (CORE_STOP/cstop_stop_library).
[core_stop] core_superv has stopped successfully (CORE_STOP/cstop_stop_superv)
2. Check which disk must be extended, the disk is the one mounted on /mnt/CACHE
[NODEUM:root]/usr/mtc/bin>df -lh
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 146G 88G 52G 64% /
tmpfs 1,9G 40K 1,9G 1% /dev/shm
/dev/sda1 465M 39M 402M 9% /boot
/dev/sdb1 886G 7,4G 834G 1% /mnt/CACHE
3. Umount the Cache disk
[NODEUM:root]/usr/mtc/bin>umount /mnt/CACHE
[NODEUM:root]/usr/mtc/bin>mount
/dev/sda2 on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
/dev/sda1 on /boot type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
4. Check the disk
sanity, if there are errors that are not fixed automatically, stop here (fix them before going to the next step)
[NODEUM:root]/usr/mtc/bin>e2fsck -f -y -v -C 0 /dev/sdb1 |
5. use parted to extend the partition size
[NODEUM:root]/usr/mtc/bin>parted /dev/sdb
(parted) unit s
(parted) print free
Modèle: VMware Virtual disk (scsi)
Disque /dev/sdb : 2097152000s
Taille des secteurs (logiques/physiques): 512B/512B
Table de partitions : gpt
Numéro Début Fin Taille Système de fichiers Nom Fanions
34s 2047s 2014s Espace libre
1 2048s 1887434751s 1887432704s ext4 primary
1887434752s 2097151966s 209717215s Espace libre
(parted) rm 1
(parted) mkpart primary 2048s 2097151966s
(parted) print free
Modèle: VMware Virtual disk (scsi)
Disque /dev/sdb : 2097152000s
Taille des secteurs (logiques/physiques): 512B/512B
Table de partitions : gpt
Numéro Début Fin Taille Système de fichiers Nom Fanions
34s 2047s 2014s Espace libre
1 2048s 2097151966s 2097149919s ext4 primary
(parted) quit
6. Check the disk again
[NODEUM:root]/usr/mtc/bin>e2fsck -f -y -v -C 0 /dev/sdb1 |
7. Extend the disk size
[NODEUM:root]/usr/mtc/bin>resize2fs -p /dev/sdb1 |
If the operation fails, see Cautions 1 above.
8. Mount the disk
[NODEUM:root]/usr/mtc/bin>mount /dev/sdb1 /mnt/CACHE/ -o user_xattr
[NODEUM:root]/usr/mtc/bin>df -lh
Filesystem Size Used Avail Use% Mounted on
/dev/sda2 146G 88G 52G 64% /
tmpfs 1,9G 32K 1,9G 1% /dev/shm
/dev/sda1 465M 39M 402M 9% /boot
/dev/sdb1 985G 7,4G 927G 1% /mnt/CACHE
9. Start the Nodeum services
[NODEUM:root]/usr/mtc/bin>./core_start all
[core_start] core_superv has started successfully (CORE_START/cstart_start_superv).
[core_start] library_manager has started successfully (CORE_START/cstart_start_library).
[core_start] core_manager has started successfully (CORE_START/cstart_start_manager).
[core_start] data_mining has started successfully (CORE_START/cstart_start_data_mining).
[core_start] core_fuse has started successfully (CORE_START/cstart_start_fuse).
[core_start] core_watchdog has started successfully (CORE_START/cstart_start_watchdog).
%20W%26G%20Dark%20Back_150px.png?width=70&name=Nodeum(Single)%20W%26G%20Dark%20Back_150px.png)
Let Us Know What You Thought about this Post.
Put your Comment Below.