So apparently, dm-0 is associated with the LVM group called VolGroup00 originally created and where vertica6 was installed (actual device name is sda). When I attempt to set the read ahead using the blockdev command, it needs a device reference. The device reference below worked: /sbin/blockdev --se...

I know its not supported on LVMs. I've migrated my vertica6 data files onto non-LVM partitions and now ran the vertica upgrade to vertica7 and get those messages. None of my /data and /catalog files exist on LVM partitions across all nodes. So how do I upgrade? Or am I done at this point?

Hi, I also am having difficulty upgrading from vetica6 to 7. These are the messages: HINT (S0151): https://my.vertica.com/docs/7.0.x/HTML/index.htm#cshid=S0151 These disks do not have known IO schedulers: '/dev/mapper/VolGroup00-LogVol00' ('dm-0') = '' HINT (S0231): https://my.vertica.com/docs/7.0.x...

Hi, I'm looking for a way to check vertica's status (up or down) from a remote server by executing a shell script. Has anyone created one they can share?
Thanks,
Joe

I have also encountered this error message when trying to backup the DB:

/opt/vertica/bin/vbr.py --task backup --config-file /Joe/IM2.2.0.0/backupConfigFile
Preparing...
Another vbr instance is running
backup failed!

I looked for all python processes but cannot find another vbr instance.