Increasing size of /data partition in vRSLCM 8.x
- Arun Nukula
- Sep 16, 2022
- 10 min read
Have a usecase to increase size of vRSLCM appliance's data partition
Current settings of the partitions on appliance
root@dlcm [ ~ ]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 2.9G 0 2.9G 0% /dev
tmpfs 3.0G 20K 3.0G 1% /dev/shm
tmpfs 3.0G 1.1M 3.0G 1% /run
tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup
/dev/sda4 8.7G 2.1G 6.2G 26% /
tmpfs 3.0G 8.4M 2.9G 1% /tmp
/dev/sda2 119M 28M 85M 25% /boot
/dev/mapper/stroage_vg-storage 9.8G 95M 9.2G 2% /storage
/dev/mapper/data_vg-data 148G 23G 119G 16% /data
tmpfs 595M 0 595M 0% /run/user/0From vCenter
PVDISPLAY output
root@dlcm [ ~ ]# pvdisplay
--- Physical volume ---
PV Name /dev/sdc
VG Name stroage_vg
PV Size <10.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2559
Free PE 0
Allocated PE 2559
PV UUID 1FzPjT-ESCV-7HMn-OdXG-Sbof-d2HM-ChEzXg
--- Physical volume ---
PV Name /dev/sdb
VG Name data_vg
PV Size <150.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 38399
Free PE 0
Allocated PE 38399
PV UUID 3xS6lh-0rjq-1HV5-kO9y-Tc5m-AYVR-uWDdpW
--- Physical volume ---
PV Name /dev/sdd
VG Name swap_vg
PV Size <8.00 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2047
Free PE 0
Allocated PE 2047
PV UUID XHQmv4-yaGc-tBbE-qg9r-Jyto-HREF-1bPNsy
Here's the /etc/fstab data for partitions. Since we are only concerned for /data , we will only work with
#system mnt-pt type options,nosuid,nodev dump fsck
/dev/sda4 / ext3 defaults 1 1
/dev/sda3 swap swap defaults 0 0
/dev/sda2 /boot ext3 defaults,nosuid,noacl,nodev,noexec 1 2
/dev/cdrom /mnt/cdrom iso9660 ro,noauto,nosuid,nodev 0 0
/dev/data_vg/data /data ext3 rw,nosuid,nodev,exec,auto,nouser,async 0 1
/dev/stroage_vg/storage /storage ext3 rw,nosuid,nodev,exec,auto,nouser,async 0 1
/dev/swap_vg/swap1 none swap sw 0 0Increased disk size of hard disk 2 from 150GB to 200GB
Now that the disk size is increased on the appliance level reboot appliance
The moment appliance is back online or responding over network ssh and execute below command " df -h "
root@dlcm [ ~ ]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 2.9G 0 2.9G 0% /dev
tmpfs 3.0G 20K 3.0G 1% /dev/shm
tmpfs 3.0G 1.1M 3.0G 1% /run
tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup
/dev/sda4 8.7G 2.1G 6.2G 26% /
tmpfs 3.0G 72K 3.0G 1% /tmp
/dev/sda2 119M 28M 85M 25% /boot
/dev/mapper/stroage_vg-storage 9.8G 95M 9.2G 2% /storage
/dev/mapper/data_vg-data 197G 23G 166G 12% /data
tmpfs 595M 0 595M 0% /run/user/0As one can see it was 150G before and the current state is 200G
How does this work ?
Below snippets are taken from journalctl -x
When you reboot after increasing the space during every reboot everyboot scripts are triggered
Sep 16 07:33:56 dlcm.cap.org vaos[959]: This script is executed on all boots, except the first one.
Sep 16 07:33:56 dlcm.cap.org vaos[959]: ++ basename /usr/lib/bootstrap/everyboot
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + NAME=everyboot
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + BOOTSTRAP_DIR=/etc/bootstrap/everyboot.d
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + BOOTSTRAP_LOG=/var/log/bootstrap/everyboot.log
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + tee -a /var/log/bootstrap/everyboot.log
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + set -eu
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + set -x
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + log 'main bootstrap everyboot started'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: ++ date '+%Y-%m-%d %H:%M:%S'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + echo '2022-09-16 07:33:56 main bootstrap everyboot started'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: 2022-09-16 07:33:56 main bootstrap everyboot started
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + for script in "${BOOTSTRAP_DIR}"/*
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + echo
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + '[' '!' -e /etc/bootstrap/everyboot.d/20-autogrow-disk ']'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + '[' '!' -x /etc/bootstrap/everyboot.d/20-autogrow-disk ']'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + log '/etc/bootstrap/everyboot.d/20-autogrow-disk starting'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: ++ date '+%Y-%m-%d %H:%M:%S'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + echo '2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting'
Sep 16 07:33:56 dlcm.cap.org vaos[959]: 2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting
Sep 16 07:33:56 dlcm.cap.org vaos[959]: + /etc/bootstrap/everyboot.d/20-autogrow-disk
Sep 16 07:33:56 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:56 UTC 2022 Disk Util: INFO: Scanning Hard disk sizes
Sep 16 07:33:56 dlcm.cap.org rsyslogd[712]: imjournal: journal files changed, reloading... [v8.2202.0 try https://www.rsyslog.com/e/0 ]
Sep 16 07:33:56 dlcm.cap.org vaos[959]: Syncing file systems
Sep 16 07:33:56 dlcm.cap.org vaos[959]: which: no multipath in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/vmware/bin)
Sep 16 07:33:56 dlcm.cap.org vaos[959]: Scanning SCSI subsystem for new devices and remove devices that have disappeared
Sep 16 07:33:56 dlcm.cap.org vaos[959]: Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs
Sep 16 07:33:57 dlcm.cap.org vaos[959]: [65B blob data]
Sep 16 07:33:57 dlcm.cap.org vaos[959]: OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Sep 16 07:33:57 dlcm.cap.org vaos[959]: Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00
Sep 16 07:33:57 dlcm.cap.org vaos[959]: Type: CD-ROM ANSI SCSI revision: 05
Sep 16 07:33:58 dlcm.cap.org vaos[959]: [182B blob data]
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: CD-ROM ANSI SCSI revision: 05
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs
Sep 16 07:33:58 dlcm.cap.org vaos[959]: [65B blob data]
Sep 16 07:33:58 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:58 dlcm.cap.org vaos[959]: [53B blob data]
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:58 dlcm.cap.org vaos[959]: [65B blob data]
Sep 16 07:33:58 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:58 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:59 dlcm.cap.org vaos[959]: [53B blob data]
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:59 dlcm.cap.org vaos[959]: [65B blob data]
Sep 16 07:33:59 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:59 dlcm.cap.org vaos[959]: [53B blob data]
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:59 dlcm.cap.org vaos[959]: [65B blob data]
Sep 16 07:33:59 dlcm.cap.org vaos[959]: OLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:59 dlcm.cap.org vaos[959]: [53B blob data]
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Vendor: VMware Model: Virtual disk Rev: 1.0
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Type: Direct-Access ANSI SCSI revision: 02
Sep 16 07:33:59 dlcm.cap.org vaos[959]: 0 new or changed device(s) found.
Sep 16 07:33:59 dlcm.cap.org vaos[959]: 0 remapped or resized device(s) found.
Sep 16 07:33:59 dlcm.cap.org vaos[959]: 0 device(s) removed.
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sda
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdb
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Physical volume "/dev/sdb" changed
Sep 16 07:33:59 dlcm.cap.org vaos[959]: 1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Sep 16 07:33:59 dlcm.cap.org vaos[959]: Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdc
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Physical volume "/dev/sdc" changed
Sep 16 07:34:00 dlcm.cap.org vaos[959]: 1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdd
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Physical volume "/dev/sdd" changed
Sep 16 07:34:00 dlcm.cap.org vaos[959]: 1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/stroage_vg/storage
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Size of logical volume stroage_vg/storage unchanged from <10.00 GiB (2559 extents).
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Logical volume stroage_vg/storage successfully resized.
Sep 16 07:34:00 dlcm.cap.org vaos[959]: resize2fs 1.45.5 (07-Jan-2020)
Sep 16 07:34:00 dlcm.cap.org vaos[959]: The filesystem is already 2620416 (4k) blocks long. Nothing to do!
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/data_vg/data
Sep 16 07:34:00 dlcm.cap.org vaos[959]: Size of logical volume data_vg/data changed from <150.00 GiB (38399 extents) to <200.00 GiB (51199 extents).
Sep 16 07:34:01 dlcm.cap.org vaos[959]: Logical volume data_vg/data successfully resized.Sep 16 07:34:01 dlcm.cap.org vaos[959]: resize2fs 1.45.5 (07-Jan-2020)
Sep 16 07:34:01 dlcm.cap.org kernel: EXT4-fs (dm-1): resizing filesystem from 39320576 to 52427776 blocks
Sep 16 07:34:01 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:01,289 main ERROR Unable to locate appender "MaskedLogs" for logger config "root"
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:05,233 main ERROR Unable to locate appender "MaskedLogs" for logger config "root"
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: . ____ _ __ _ _
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: \\/ ___)| |_)| | | | | || (_| | ) ) ) )
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: ' |____| .__|_| |_|_| |_\__, | / / / /
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: =========|_|==============|___/=/_/_/_/
Sep 16 07:34:05 dlcm.cap.org launch-blackstone-spring[1099]: :: Spring Boot :: (v2.1.16.RELEASE)
Sep 16 07:34:06 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:06.313 INFO dlcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStarting] : Start>
Sep 16 07:34:06 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:06.368 DEBUG dlcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStarting] : Runni>
Sep 16 07:34:06 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:06.369 INFO dlcm.cap.org --- [ main] c.v.b.BlackstoneExternalApplication [logStartupProfileInf>
Sep 16 07:34:07 dlcm.cap.org systemd-resolved[1403]: Using degraded feature set (UDP+EDNS0) for DNS server 10.109.44.132.
Sep 16 07:34:11 dlcm.cap.org kernel: EXT4-fs (dm-1): resized to 46792704 blocks
Sep 16 07:34:11 dlcm.cap.org vlcm-service[1098]: [2022-09-16 07:34:11.274] [INFO ][main] org.spr.con.sup.PostProcessorRegistrationDelegate$BeanPostProcessorChecker: -- Bean 'configuratio>
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: [2022-09-16 07:34:12.102] [INFO ][main] com.vmw.vre.lcm.com.log.MaskingPrintStream: -- * SYSOUT/SYSERR CAPTURED: --
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: ___ ___ _ ___ __ __
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: __ __ | _ \ / __| | | / __| | \/ |
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: \ V / | / \__ \ | |__ | (__ | |\/| |
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _\_/_ |_|_\ |___/ |____| \___| |_| |_|
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _|"""""| _|"""""| _|"""""| _|"""""| _|"""""| _|"""""|
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-'
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: * --
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: ___ ___ _ ___ __ __
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: __ __ | _ \ / __| | | / __| | \/ |
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: \ V / | / \__ \ | |__ | (__ | |\/| |
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _\_/_ |_|_\ |___/ |____| \___| |_| |_|
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: _|"""""| _|"""""| _|"""""| _|"""""| _|"""""| _|"""""|
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-' "`-0-0-'
Sep 16 07:34:12 dlcm.cap.org vlcm-service[1098]: [2022-09-16 07:34:12.156] [INFO ][main] org.spr.boo.SpringApplication: -- The following profiles are active: apiignore
Sep 16 07:34:15 dlcm.cap.org launch-blackstone-spring[1099]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
Sep 16 07:34:15 dlcm.cap.org launch-blackstone-spring[1099]: SLF4J: Defaulting to no-operation (NOP) logger implementation
Sep 16 07:34:15 dlcm.cap.org launch-blackstone-spring[1099]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Sep 16 07:34:17 dlcm.cap.org launch-blackstone-spring[1099]: 2022-09-16 07:34:17.856 INFO dlcm.cap.org --- [ main] trationDelegate$BeanPostProcessorChecker [postProcessAfterInit>
Sep 16 07:34:19 dlcm.cap.org kernel: EXT4-fs (dm-1): resized filesystem to 52427776
Sep 16 07:34:19 dlcm.cap.org vaos[959]: Filesystem at /dev/mapper/data_vg-data is mounted on /data; on-line resizing required
Sep 16 07:34:19 dlcm.cap.org vaos[959]: old_desc_blocks = 10, new_desc_blocks = 13
Sep 16 07:34:19 dlcm.cap.org vaos[959]: The filesystem on /dev/mapper/data_vg-data is now 52427776 (4k) blocks long.
Sep 16 07:34:19 dlcm.cap.org vaos[959]: Fri Sep 16 07:34:19 UTC 2022 Disk Util: INFO: LV Resizing /dev/swap_vg/swap1
Sep 16 07:34:19 dlcm.cap.org vaos[959]: fsadm: Filesystem "swap" on device "/dev/mapper/swap_vg-swap1" is not supported by this tool.
Sep 16 07:34:19 dlcm.cap.org vaos[959]: Filesystem check failed.
Sep 16 07:34:20 dlcm.cap.org vaos[959]: + RES=0
Sep 16 07:34:20 dlcm.cap.org vaos[959]: + log '/etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0'
Sep 16 07:34:20 dlcm.cap.org vaos[959]: ++ date '+%Y-%m-%d %H:%M:%S'
Sep 16 07:34:20 dlcm.cap.org vaos[959]: + echo '2022-09-16 07:34:20 /etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0'
Sep 16 07:34:20 dlcm.cap.org vaos[959]: 2022-09-16 07:34:20 /etc/bootstrap/everyboot.d/20-autogrow-disk done, status: 0
This is the script where it's located
Log Snippet from everyboot.log under /var/log/bootstrap/
+ echo '2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting'
2022-09-16 07:33:56 /etc/bootstrap/everyboot.d/20-autogrow-disk starting
+ /etc/bootstrap/everyboot.d/20-autogrow-disk
Fri Sep 16 07:33:56 UTC 2022 Disk Util: INFO: Scanning Hard disk sizes
Syncing file systems
which: no multipath in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/vmware/bin)
Scanning SCSI subsystem for new devices and remove devices that have disappeared
Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs
Scanning for device 0 0 0 0 ...^M Scanning for device 0 0 0 0 ...
OLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 05
.0:0:0:0 sg0 (1) ESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[D ESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[DESC[D
ESC[D^MESC[AESC[AESC[AOLD: Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: NECVMWar Model: VMware IDE CDR00 Rev: 1.00
Type: CD-ROM ANSI SCSI revision: 05
Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs
Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15, all LUNs
Scanning for device 2 0 0 0 ...^M Scanning for device 2 0 0 0 ...
OLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
Scanning for device 2 0 1 0 ...^M Scanning for device 2 0 1 0 ...
OLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 01 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
Scanning for device 2 0 2 0 ...^M Scanning for device 2 0 2 0 ...
OLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 02 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
Scanning for device 2 0 3 0 ...^M Scanning for device 2 0 3 0 ...
OLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
^MESC[AESC[AESC[AOLD: Host: scsi2 Channel: 00 Id: 03 Lun: 00
Vendor: VMware Model: Virtual disk Rev: 1.0
Type: Direct-Access ANSI SCSI revision: 02
0 new or changed device(s) found.
0 remapped or resized device(s) found.
0 device(s) removed.
Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sda
Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdb
Physical volume "/dev/sdb" changed
1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Fri Sep 16 07:33:59 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdc
Physical volume "/dev/sdc" changed
1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: Resizing PV /dev/sdd
Physical volume "/dev/sdd" changed
1 physical volume(s) resized or updated / 0 physical volume(s) not resized
Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/stroage_vg/storage
Size of logical volume stroage_vg/storage unchanged from <10.00 GiB (2559 extents).
Logical volume stroage_vg/storage successfully resized.
resize2fs 1.45.5 (07-Jan-2020)
The filesystem is already 2620416 (4k) blocks long. Nothing to do!
Fri Sep 16 07:34:00 UTC 2022 Disk Util: INFO: LV Resizing /dev/data_vg/data
Size of logical volume data_vg/data changed from <150.00 GiB (38399 extents) to <200.00 GiB (51199 extents).
Logical volume data_vg/data successfully resized.
resize2fs 1.45.5 (07-Jan-2020)
Filesystem at /dev/mapper/data_vg-data is mounted on /data; on-line resizing required
old_desc_blocks = 10, new_desc_blocks = 13
Kommentare