Yesterday the disk where the catalog and data directories are mounted, /dev/mapper/mpatha1, was pointed to ../dm-4, and now today it is pointing to ../dm-5.
Is it OK if these change as long as the readahead and blocksize are correct? Vertica is up and running and seems to be fine.
The change only appears to happen sometimes when we reboot the server.
[[email protected] ~]# ls -l /dev/mapper/mpatha1
lrwxrwxrwx. 1 root root 7 Jan 11 18:12 /dev/mapper/mpatha1 -> ../dm-5
[[email protected] ~]#
[[email protected] ~]$ ls -l /dev/mapper/mpatha1
lrwxrwxrwx. 1 root root 7 Jan 12 04:14 /dev/mapper/mpatha1 -> ../dm-4
[[email protected] ~]$
[[email protected] server diagnostics]# mount | grep apps
/dev/mapper/mpatha1 on /apps type ext4 (rw,relatime,seclabel,data=ordered)
[[email protected] server diagnostics]# sudo -u dradmin /opt/vertica/bin/admintools -t list_allnodes
Node | Host | State | Version | DB
v_drdata_node0001 | 142.145105.110 | UP | vertica-184.108.40.206 | drdata
v_drdata_node0002 | 220.127.116.11 | UP | vertica-18.104.22.168 | drdata
v_drdata_node0003 | 22.214.171.124 | UP | vertica-126.96.36.199 | drdata
/dev/mapper/mpatha1 is not a single path to storage it is in this case a representative of 4 paths and luns that have been defined to the system.
The system uses one of the 4 paths at a time. If one of the paths go down, slow, system booted , or other thing the system redirects data to an up path.
Dm names are based on a low level Device Manager module it is not LVM but it is above basic formatting of disks. So probably there are 4 dm names it can float to and you’ve only seen 2.
Release : 20.2
Component : IMSTORE
CAPM only cares that it's properly mounted to a disk partition.
How the OS and SAN route it to the end disk with the data doesn't matter.
It's on the user to ensure it's properly mounted to the correct location and that whatever they're using allows proper access while meeting the necessary I/O requirements, etc.