Open mumutyal opened 4 years ago
After portworx installation
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1000G 0 disk
└─3600a09803830476f522b4e4451724e53 253:1 0 1000G 0 mpath
sdb 8:16 0 1000G 0 disk
└─3600a09803830476f522b4e4451724e53 253:1 0 1000G 0 mpath
xvda 202:0 0 25G 0 disk
├─xvda1 202:1 0 1G 0 part /boot
└─xvda2 202:2 0 24G 0 part /
xvdb 202:16 0 2G 0 disk
└─xvdb1 202:17 0 2G 0 part [SWAP]
xvdc 202:32 0 100G 0 disk
└─docker_data 253:0 0 100G 0 crypt /var/data
xvdh 202:112 0 64M 0 disk
└─xvdh1 202:113 0 61M 0 part
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]#
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 32G 0 32G 0% /dev
/dev/shm 32G 8.0K 32G 1% /dev/shm
tmpfs 32G 146M 32G 1% /run
tmpfs 32G 0 32G 0% /sys/fs/cgroup
/dev/xvda2 24G 6.4G 16G 29% /
/dev/xvda1 976M 92M 834M 10% /boot
/dev/mapper/docker_data 99G 6.4G 87G 7% /var/data
shm 64M 0 64M 0% /var/data/crioruntimestorage/overlay-containers/ba371800fe19b6c0954462619951e451b0160bf8c91b7c2e32f0f5875abd9280/userdata/shm
overlay 99G 6.4G 87G 7% /var/data/criorootstorage/overlay/383cc8060374df6e164843c5cdce19db5b90aa9091f28efbaaa51a1745c33fd2/merged
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]# ls -a /etc/pwx
. .. config.json etcdcerts .lic .private.json px_env .px_fspatch
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]# du /dev/sda
0 /dev/sda
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]# du /dev/sdb
0 /dev/sdb
[root@kube-bqadr53w09q9gff6ji3g-dansandydeb-default-00000382 /]#
The portworx does not use the remote volumes to store its information it will be stored in the local or secondary disks
@sandaymin123 : As seen above, the usage of /dev/xvda2
was 18% before Portworx install and it went to 29% after install. This is the secondary disk on worker node the path where Portworx fimgerprints are stored is /etc/pwx
which part of /dev/xvda2
.
The remote block volume is /dev/sda
above its not used for Portworx fimgerprint.
The usage of remote block volume is not affecting in any way for Portworx deploy and we can re-use the same volume for multiple deploys. The worker nodes need to be wiped from Portworx fingerprint for multiple deploys.
We created remote volumes and attached to the worker nodes of the cluster and the following is the usage and size info before installation of the portworx
Before portworx installation