Upgrade from Vertica 6.1 to Vertica 7.0

Moderator: NorbertKrupa

mohjo01
Newbie
Newbie
Posts: 5
Joined: Thu Feb 21, 2013 7:35 pm

Re: Upgrade from Vertica 6.1 to Vertica 7.0

Post by mohjo01 » Tue Aug 12, 2014 10:20 pm

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/ ... shid=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/HTML/ ... shid=S0231
dbadmin user ('dradmin') primary group is not verticadba ('verticadba')
HINT (S0305): https://my.vertica.com/docs/7.0.x/HTML/ ... shid=S0305
TZ is unset for dradmin. Consider updating .profile or .bashrc
HINT (S0040): https://my.vertica.com/docs/7.0.x/HTML/ ... shid=S0040
Could not find the following tools normally provided by the pstack or
gstack package: pstack/gstack
HINT (S0045): https://my.vertica.com/docs/7.0.x/HTML/ ... shid=S0045
Could not find the following tools normally provided by the sysstat
package: mpstat, iostat
WARN (S0170): https://my.vertica.com/docs/7.0.x/HTML/ ... shid=S0170
lvscan (LVM utility) indicates some active volumes.
FAIL (S0020): https://my.vertica.com/docs/7.0.x/HTML/ ... shid=S0020
Readahead size of dm-0 (/dev/mapper/VolGroup00-LogVol00) is too low for
typical systems: 256 < 2048

This FAIl at the end is the one in question. The only dm-0 I have is located here:
/sys/block/sda/sda2/holders/dm-0:
-r--r--r-- 1 root root 4096 Aug 8 18:11 dev
drwxr-xr-x 2 root root 0 Aug 8 18:11 holders
-r--r--r-- 1 root root 4096 Aug 8 18:11 range
-r--r--r-- 1 root root 4096 Aug 8 18:11 removable
-r--r--r-- 1 root root 4096 Aug 8 18:11 size
drwxr-xr-x 2 root root 0 Aug 8 18:11 slaves
-r--r--r-- 1 root root 4096 Aug 8 18:11 stat
lrwxrwxrwx 1 root root 0 Aug 8 18:11 subsystem -> ../../block
--w------- 1 root root 4096 Aug 8 18:11 uevent


I executed this command for the sda device (also on the other 2 devices I have, sdb and sdc):
/sbin/blockdev --setra 2048 /dev/sda

/sbin/blockdev --getra /dev/sda gives me:
2048

So how do I change dm-0?

Thanks in advance,
Joe

id10t
GURU
GURU
Posts: 732
Joined: Mon Apr 16, 2012 2:44 pm

Re: Upgrade from Vertica 6.1 to Vertica 7.0

Post by id10t » Wed Aug 13, 2014 2:15 pm

Hi!

[DELETED]
Last edited by id10t on Wed May 06, 2015 4:48 pm, edited 1 time in total.

mohjo01
Newbie
Newbie
Posts: 5
Joined: Thu Feb 21, 2013 7:35 pm

Re: Upgrade from Vertica 6.1 to Vertica 7.0

Post by mohjo01 » Wed Aug 13, 2014 3:05 pm

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?

mohjo01
Newbie
Newbie
Posts: 5
Joined: Thu Feb 21, 2013 7:35 pm

Re: Upgrade from Vertica 6.1 to Vertica 7.0

Post by mohjo01 » Wed Aug 13, 2014 5:40 pm

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 --setra 2048 /dev/mapper/VolGroup00-LogVol00
(There is also a VolGroup01 which did not require read ahead adjustment.)
And thus the vertica6 to 7 upgrade worked.

Best Regards,
Joe

Post Reply

Return to “Vertica Upgrade”