Forum Discussion

Sylvain_85827's avatar
Sylvain_85827
Icon for Cirrus rankCirrus
Jun 23, 2015
Solved

VCMP space disk allocation explanations

Hello, Can please someone help me to understand the disk allocation of this VCMP system? 1/ Total physical disk space is : 400GB according to fdisk: [root@XXX:Active:Standalone] config fdisk ...
management
storage
TMSH
virtualization
  • Jim_43841's avatar
    Jim_43841
    Jun 25, 2015

    Yes, those set.N items are related to the install locations HD1.N. If you want to destroy one, you can issue "tmsh delete sys software volume HD1.N", either in the guest or the host, wherever you're trying to eke out more free disk space.

     

Sylvain_85827's avatar
Sylvain_85827
Icon for Cirrus rankCirrus
Jun 25, 2015

Thanks Jim, for your help.

Lvscan command returns this:

[root@XXX:Active:Standalone] config  lvscan -av
    Finding all logical volumes
  ACTIVE            '/dev/vg-db-sda/dat.boot' [372.00 MB] inherit
  ACTIVE            '/dev/vg-db-sda/dat.share.1' [30.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/dat.log.1' [7.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/dat.swapvol.1' [5.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.1.root' [392.00 MB] inherit
  ACTIVE            '/dev/vg-db-sda/set.1._usr' [2.20 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.1._config' [3.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.1._var' [3.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.2.root' [392.00 MB] inherit
  ACTIVE            '/dev/vg-db-sda/set.2._usr' [2.48 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.2._config' [3.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.2._var' [3.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/app.vcmp.dat.vmdisks' [276.72 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.3.root' [392.00 MB] inherit
  ACTIVE            '/dev/vg-db-sda/set.3._usr' [2.48 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.3._config' [3.00 GB] inherit
  ACTIVE            '/dev/vg-db-sda/set.3._var' [3.00 GB] inherit

Do you know all these "set.*_*" volumes are all necessary? Can the "missing" space coming from there:

'/dev/vg-db-sda/set.1._usr' 
'/dev/vg-db-sda/set.1.root' 
'/dev/vg-db-sda/set.1._config' 
'/dev/vg-db-sda/set.1._var' 
'/dev/vg-db-sda/set.2.root' 
'/dev/vg-db-sda/set.2._usr' 
'/dev/vg-db-sda/set.2._config' 
'/dev/vg-db-sda/set.2._var' 
'/dev/vg-db-sda/set.3.root' 
'/dev/vg-db-sda/set.3._usr' 
'/dev/vg-db-sda/set.3._config' 
'/dev/vg-db-sda/set.3._var'

What do you suggest please?

Thanks again for your help.

Sylvain

  • Sylvain_85827's avatar
    Sylvain_85827
    Icon for Cirrus rankCirrus
    Jun 25, 2015
    Maybe I just found the explanation thanks to you Jim. You're right there are 3 installations installed respectively on HD1.1, HD1.2 and HD1.3 as boot locations. Can you confirm if this corresponds to /dev/vg-db-sda/set.1* , /dev/vg-db-sda/set.2* and /dev/vg-db-sda/set.3* ? If you do, I think we found the culprit ;-) Cheers. Sylvain