Linux – Online configuration of new SAN disks to create new sybase raw volumes, using LVM.

As part of regular System Admin task we were asked to configure new storage to an existing sybase server without disturbing the existing storage and expecting no downtime for the existing production server. All necessary storage LUNS were already allocated by the Storage team as mentioned below


LUNS allocated by storage Team

Lun 011D
Lun 011E
Lun 011F
Lun 0167
Lun 017E
Lun 01F0

DBA team requested System Admin team to create below raw volumes in an existing Volume Group named sybasevg.

Raw – Volumes To be created in SybaseVG volume Group:

data01-new-rawvol
data02-new-rawvol
data03-new-rawvol
logs01-new-rawvol
master-new-rawvol
procs-new-rawvol

In SybaseVG there are already some old volumes exist and we have to configure the new volumes without disturbing below existing volumes in Sybase VG:

data01-old-vol
data02-old-vol
data03-old-vol
data04-old-vol
data05-old-vol
data06-old-vol
data07-old-vol
log01-old-vol
master_old_vol
procs_old_vol

Phase 1 – A Quick look at existing Volume / Disk configuration

Displaying Existing Volume Group Names from the System

[root@gurkulindia-linuxserver>> mapper]# vgs
VG #PV #LV #SN Attr VSize VFree
sybasevg 13 16 0 wz–n- 310.59G 4.12G

Displaying Complete VG information from the System

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgdisplay -v
Finding all volume groups
Finding volume group “sybasevg”
— Volume group —
VG Name sybasevg
System ID
Format lvm2
Metadata Areas 13
Metadata Sequence No 49
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 16
Open LV 10
Max PV 0
Cur PV 13
Act PV 13
VG Size 310.59 GB
PE Size 4.00 MB
Total PE 79510
Alloc PE / Size 78455 / 306.46 GB
Free PE / Size 1055 / 4.12 GB
VG UUID eUI2NE-cByi-0kzF-Ccs3-sZLq-IQc3-xdap9E

— Logical volume —
LV Name /dev/sybasevg/master_old_vol
VG Name sybasevg
LV UUID jtmA3G-XdYV-fwXO-6o5M-0DKS-VRCT-ItdWHl
LV Write Access read/write
LV Status available
# open 3
LV Size 300.00 MB
Current LE 75
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:19

— Logical volume —
LV Name /dev/sybasevg/procs_old_vol
VG Name sybasevg
LV UUID 3cTQWT-eOaf-EYTQ-AVla-Lug6-Wq2y-Gi6c7a
LV Write Access read/write
LV Status available
# open 3
LV Size 720.00 MB
Current LE 180
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:20

— Logical volume —
LV Name /dev/sybasevg/data01-old-vol
VG Name sybasevg
LV UUID 3ij1Mi-A8CX-5GGR-WtqO-3IsF-Vvz7-VbvWF5
LV Write Access read/write
LV Status available
# open 3
LV Size 29.30 GB
Current LE 7500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:21

— Logical volume —
LV Name /dev/sybasevg/data02-old-vol
VG Name sybasevg
LV UUID 8INe45-22I3-HcNG-9F0h-p37k-OwsV-gel3ti
LV Write Access read/write
LV Status available
# open 3
LV Size 29.30 GB
Current LE 7500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:22

— Logical volume —
LV Name /dev/sybasevg/data03-old-vol
VG Name sybasevg
LV UUID aiAyuZ-MFuV-NMzh-ass1-NPRq-mMfU-zvkqfM
LV Write Access read/write
LV Status available
# open 1
LV Size 29.30 GB
Current LE 7500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:23

— Logical volume —
LV Name /dev/sybasevg/data04-old-vol
VG Name sybasevg
LV UUID b8t5CE-LDWW-NQ8Q-y0xi-L6gP-Rfyf-yr5fgz
LV Write Access read/write
LV Status available
# open 1
LV Size 9.77 GB
Current LE 2500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:24

— Logical volume —
LV Name /dev/sybasevg/log01-old-vol
VG Name sybasevg
LV UUID CVlpgx-utHs-DsGe-vpJ2-Qs3d-79v8-9gnNqo
LV Write Access read/write
LV Status available
# open 3
LV Size 19.53 GB
Current LE 5000
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:25

— Logical volume —
LV Name /dev/sybasevg/data05-old-vol
VG Name sybasevg
LV UUID Us8geK-QcUb-Hb06-tb1U-gOVg-1m79-BTChun
LV Write Access read/write
LV Status available
# open 1
LV Size 29.30 GB
Current LE 7500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:26

— Logical volume —
LV Name /dev/sybasevg/data06-old-vol
VG Name sybasevg
LV UUID ZGK3LB-kf3x-r9uu-1clB-HWvR-E0om-awGACF
LV Write Access read/write
LV Status available
# open 3
LV Size 29.30 GB
Current LE 7500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:27

— Logical volume —
LV Name /dev/sybasevg/data07-old-vol
VG Name sybasevg
LV UUID ktWDSB-zQaW-cRBM-hVa1-yzaf-e1pM-iPheXx
LV Write Access read/write
LV Status available
# open 3
LV Size 29.30 GB
Current LE 7500
Segments 1
Allocation inherit
Read ahead sectors auto
– currently set to 256
Block device 253:28

— Physical volumes —
PV Name /dev/dm-11
PV UUID GM16UB-Ecej-bwJN-QFw0-JYGT-fQwH-VDqr0e
PV Status allocatable
Total PE / Free PE 7680 / 0

PV Name /dev/dm-12
PV UUID SftHhf-YPY5-1msC-JkcV-F1R0-BQ1o-YrYiLG
PV Status allocatable
Total PE / Free PE 7680 / 156

PV Name /dev/dm-13
PV UUID kuKBL6-e1bW-kXLO-OFH1-N7WM-rfdP-nBQnuM
PV Status allocatable
Total PE / Free PE 7680 / 180

PV Name /dev/dm-14
PV UUID WGcErf-1ku6-Y513-wLb2-BvlV-ngJu-eetUVH
PV Status allocatable
Total PE / Free PE 2560 / 60

PV Name /dev/dm-10
PV UUID dC8dq8-nFk0-cO8l-vuU3-odQo-WNdP-p1i5El
PV Status allocatable
Total PE / Free PE 255 / 0

PV Name /dev/dm-15
PV UUID ZQt0gh-VkQf-12Ym-sQ6a-LuU0-mpwa-1qeD0Y
PV Status allocatable
Total PE / Free PE 5119 / 119

PV Name /dev/dm-16
PV UUID L114TU-1ssc-COBg-j9ta-bzHJ-DmVa-6hayOG
PV Status allocatable
Total PE / Free PE 7680 / 180

PV Name /dev/dm-17
PV UUID R1e041-eJ4w-SWUA-0412-Rr0Q-SKFj-ru4Fyc
PV Status allocatable
Total PE / Free PE 7680 / 180

PV Name /dev/dm-18
PV UUID KkXyDp-i1GJ-GIGu-I89X-UR6g-tZnS-uncgHw
PV Status allocatable
Total PE / Free PE 7680 / 180

Displaying Existing Device files related to the sybasevg

Note : block device files available at /dev/mapper and raw device files at /dev/raw-mapper. The existing Volumes under “sybasevg” was linked to the files in /dev/mapper .

[root@gurkulindia-linuxserver>> /dev/]# cd /dev/sybasevg
[root@gurkulindia-linuxserver>> sybasevg]# ls -rlt
total 0
lrwxrwxrwx 1 root root 61 Jul 23 17:11 master_old_vol -> /dev/mapper/master_old_vol
lrwxrwxrwx 1 root root 66 Jul 23 17:11 procs_old_vol -> /dev/mapper/procs_old_vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data01-old-vol -> /dev/mapper/data01-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data02-old-vol -> /dev/mapper/data02-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data03-old-vol -> /dev/mapper/data03-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data04-old-vol -> /dev/mapper/data04-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 log01-old-vol -> /dev/mapper/logs01-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data05-old-vol -> /dev/mapper/data05-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data06-old-vol -> /dev/mapper/data06-old-vol
lrwxrwxrwx 1 root root 61 Jul 23 17:11 data07-old-vol -> /dev/mapper/data07-old-vol

[root@gurkulindia-linuxserver>> sybasevg]# cd /dev/mapper
[root@gurkulindia-linuxserver>> mapper]# ls -lrt        <– Old Volumes are underlined
total 0
crw——- 1 root root 10, 63 Jul 23 17:10 control
brw-rw—- 1 root disk 253, 3 Jul 23 17:10 rootvg-swapvol
brw-rw—- 1 root disk 253, 15 Jul 23 17:11 mpath9
brw-rw—- 1 root disk 253, 14 Jul 23 17:11 mpath8
brw-rw—- 1 root disk 253, 13 Jul 23 17:11 mpath7
brw-rw—- 1 root disk 253, 12 Jul 23 17:11 mpath6
brw-rw—- 1 root disk 253, 11 Jul 23 17:11 mpath5
brw-rw—- 1 root disk 253, 10 Jul 23 17:11 mpath4
brw-rw—- 1 root disk 253, 9 Jul 23 17:11 mpath3
brw-rw—- 1 root disk 253, 8 Jul 23 17:11 mpath2
brw-rw—- 1 root disk 253, 18 Jul 23 17:11 mpath12
brw-rw—- 1 root disk 253, 17 Jul 23 17:11 mpath11
brw-rw—- 1 root disk 253, 16 Jul 23 17:11 mpath10
brw-rw—- 1 root disk 253, 7 Jul 23 17:11 mpath1
brw-rw—- 1 root disk 253, 6 Jul 23 17:11 mpath0
brw-rw—- 1 root disk 253, 19 Jul 23 17:11 master_old_vol
brw-rw—- 1 root disk 253, 20 Jul 23 17:11 procs_old_vol
brw-rw—- 1 root disk 253, 21 Jul 23 17:11 data01-old-vol
brw-rw—- 1 root disk 253, 22 Jul 23 17:11 data02-old-vol
brw-rw—- 1 root disk 253, 23 Jul 23 17:11 data03-old-vol
brw-rw—- 1 root disk 253, 24 Jul 23 17:11 data04-old-vol
brw-rw—- 1 root disk 253, 25 Jul 23 17:11 logs01-old-vol
brw-rw—- 1 root disk 253, 26 Jul 23 17:11 data05-old-vol
brw-rw—- 1 root disk 253, 27 Jul 23 17:11 data06-old-vol
brw-rw—- 1 root disk 253, 28 Jul 23 17:11 data07-old-vol
brw-rw—- 1 root disk 253, 0 Jul 23 17:11 rootvg-rootvol
brw-rw—- 1 root disk 253, 1 Jul 23 17:11 rootvg-varvol
brw-rw—- 1 root disk 253, 5 Jul 23 17:11 rootvg-sbclocalvol
brw-rw—- 1 root disk 253, 2 Jul 23 17:11 rootvg-tmpvol
brw-rw—- 1 root disk 253, 4 Jul 23 17:11 rootvg-kdumpvol
brw-rw—- 1 root disk 253, 29 Jul 23 17:12 sybasefsdg-sybaseapp
brw-rw—- 1 root disk 253, 31 Jul 23 17:12 sybasefsdg-sybasedump
brw-rw—- 1 root disk 253, 30 Jul 23 17:12 sybasefsdg-tempdb
brw-rw—- 1 root disk 253, 35 Sep 3 13:38 mpath16
brw-rw—- 1 root disk 253, 38 Sep 3 13:38 mpath19
brw-rw—- 1 root disk 253, 32 Sep 3 13:57 mpath13
brw-rw—- 1 root disk 253, 33 Sep 3 14:18 mpath14
brw-rw—- 1 root disk 253, 34 Sep 3 14:19 mpath15
brw-rw—- 1 root disk 253, 36 Sep 3 14:20 mpath17
brw-rw—- 1 root disk 253, 37 Sep 3 14:21 mpath18

Displaying Existing Logical Volumes information – Breif View.

[root@gurkulindia-linuxserver>> mapper]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
kdumpvol rootvg -wi-ao 23.59G
rootvol rootvg -wi-ao 4.00G
sbclocalvol rootvg -wi-ao 93.97G
swapvol rootvg -wi-ao 8.00G
tmpvol rootvg -wi-ao 3.00G
varvol rootvg -wi-ao 4.00G
sybaseapp sybasefsdg -wi-ao 8.00G
sybasedump sybasefsdg -wi-ao 47.99G
tempdb sybasefsdg -wi-ao 6.00G
data01-old-vol sybasevg -wi-ao 29.30G   <– Old Volumes are underlined
data02-old-vol sybasevg -wi-ao 29.30G
data03-old-vol sybasevg -wi-ao 29.30G
data04-old-vol sybasevg -wi-ao 9.77G
data05-old-vol sybasevg -wi-ao 29.30G
data06-old-vol sybasevg -wi-ao 29.30G
data07-old-vol sybasevg -wi-ao 29.30G
log01-old-vol sybasevg -wi-ao 19.53G
master_old_vol sybasevg -wi-ao 300.00M
procs_old_vol sybasevg -wi-ao 720.00M

Displaying Existing multipath information for Storage Disks

[root@gurkulindia-linuxserver>> mapper]# multipath -ll | grep -v dm
[size=6.0G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:2 sdc 8:32 [active][ready]
_ 1:0:0:2 sdp 8:240 [active][ready]
[size=8.0G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:1 sdb 8:16 [active][ready]
_ 1:0:0:1 sdo 8:224 [active][ready]
[size=300M][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:19 sdag 66:0 [active][ready]
_ 1:0:0:19 sdan 66:112 [active][ready]
[size=2.8M][features=1 queue_if_no_path][hwhandler=0][ro]
_ round-robin 0 [prio=0][active]
_ 0:0:0:0 sda 8:0 [active][ready]
_ 1:0:0:0 sdn 8:208 [active][ready]
[size=8.0G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:18 sdaf 65:240 [active][ready]
_ 1:0:0:18 sdam 66:96 [active][ready]
[size=12G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:17 sdae 65:224 [active][ready]
_ 1:0:0:17 sdal 66:80 [active][ready]
[size=502M][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:16 sdad 65:208 [active][ready]
_ 1:0:0:16 sdak 66:64 [active][ready]
[size=20G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:9 sdj 8:144 [active][ready]
_ 1:0:0:9 sdw 65:96 [active][ready]
[size=29G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:15 sdac 65:192 [active][ready]
_ 1:0:0:15 sdaj 66:48 [active][ready]
[size=10G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:8 sdi 8:128 [active][ready]
_ 1:0:0:8 sdv 65:80 [active][ready]
[size=29G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:14 sdab 65:176 [active][ready]
_ 1:0:0:14 sdai 66:32 [active][ready]
[size=30G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:7 sdh 8:112 [active][ready]
_ 1:0:0:7 sdu 65:64 [active][ready]
[size=29G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:13 sdaa 65:160 [active][ready]
_ 1:0:0:13 sdah 66:16 [active][ready]
[size=30G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:6 sdg 8:96 [active][ready]
_ 1:0:0:6 sdt 65:48 [active][ready]
[size=30G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 1:0:0:12 sdz 65:144 [active][ready]
[size=30G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:5 sdf 8:80 [active][ready]
_ 1:0:0:5 sds 65:32 [active][ready]
[size=30G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:11 sdl 8:176 [active][ready]
_ 1:0:0:11 sdy 65:128 [active][ready]
[size=1021M][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:4 sde 8:64 [active][ready]
_ 1:0:0:4 sdr 65:16 [active][ready]
[size=30G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:10 sdk 8:160 [active][ready]
_ 1:0:0:10 sdx 65:112 [active][ready]
[size=40G][features=1 queue_if_no_path][hwhandler=0][rw]
_ round-robin 0 [prio=0][active]
_ 0:0:0:3 sdd 8:48 [active][ready]
_ 1:0:0:3 sdq 65:0 [active][ready]

[root@gurkulindia-linuxserver>> mapper]# cd /dev/raw-mapper/

Note: The files under /dev/raw-mapper are actually link files to the raw devices under /dev/raw/ . And if you want change any permissions on raw devices you should set it on the files under /dev/raw instead of the link files.

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# ls -lrt
total 0
lrwxrwxrwx 1 root root 12 Jul 23 17:11 logs01-old-vol -> ../raw/raw26
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data02-old-vol -> ../raw/raw23
lrwxrwxrwx 1 root root 12 Jul 23 17:11 procs_old_vol -> ../raw/raw21
lrwxrwxrwx 1 root root 12 Jul 23 17:11 master_old_vol -> ../raw/raw20
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data04-old-vol -> ../raw/raw25
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data03-old-vol -> ../raw/raw24
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data06-old-vol -> ../raw/raw28
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data01-old-vol -> ../raw/raw22
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data05-old-vol -> ../raw/raw27
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data07-old-vol -> ../raw/raw29
[root@gurkulindia-linuxserver>> /dev/raw-mapper]# cd /dev/raw/

[root@gurkulindia-linuxserver>> /dev/raw]# ls -rlt
total 0
crw-rw—- 1 sybase sybase 162, 25 Jul 23 17:11 raw25
crw-rw—- 1 sybase sybase 162, 24 Jul 23 17:11 raw24
crw-rw—- 1 sybase sybase 162, 27 Jul 23 17:11 raw27
crw-rw—- 1 sybase sybase 162, 29 Sep 20 18:37 raw29
crw-rw—- 1 sybase sybase 162, 28 Sep 20 18:37 raw28
crw-rw—- 1 sybase sybase 162, 22 Sep 20 18:37 raw22
crw-rw—- 1 sybase sybase 162, 21 Sep 20 18:37 raw21
crw-rw—- 1 sybase sybase 162, 20 Sep 20 18:37 raw20
crw-rw—- 1 sybase sybase 162, 23 Sep 20 18:38 raw23
crw-rw—- 1 sybase sybase 162, 26 Sep 20 18:38 raw26

Displaying Existing Storage LUN information using emc’s Inq utility.

Note: Inq utility helps you to inquire the server interms of storage information like parent Storage device , WWN, LUN ID …. etc. Comparing these outputs before and after new-storage detection will give us quick review on what was newly detected and what was existing.

[root@gurkulindia-linuxserver>> /dev/raw]# /emc-tools/inq.linux -sym_wwn -no_dots
Inquiry utility, Version V7.3-883 (Rev 1.0) (SIL Version V6.5.1.0 (Edit Level 883)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.

————————————————————————-
Symmetrix DeviceSymm Serial # Device # WWN
————————————————————————-
/dev/sda 000292600314 0002C 60000970000292600314533030303243
/dev/sdb 000292600314 002DC 60000970000292600314533030324443
/dev/sdc 000292600314 002DD 60000970000292600314533030324444
/dev/sdd 000292600314 002DE 60000970000292600314533030324445
/dev/sde 000292600314 002DF 60000970000292600314533030324446
/dev/sdf 000292600314 002E0 60000970000292600314533030324530
/dev/sdg 000292600314 002E1 60000970000292600314533030324531
/dev/sdh 000292600314 002E2 60000970000292600314533030324532
/dev/sdi 000292600314 002E3 60000970000292600314533030324533
/dev/sdj 000292600314 002E4 60000970000292600314533030324534
/dev/sdk 000292600314 00219 60000970000292600314533030323139
/dev/sdl 000292600314 0021A 60000970000292600314533030323141
/dev/sdm 000292600314 0021B 60000970000292600314533030323142
/dev/sdn 000292600314 0002C 60000970000292600314533030303243
/dev/sdo 000292600314 002DC 60000970000292600314533030324443
/dev/sdp 000292600314 002DD 60000970000292600314533030324444
/dev/sdq 000292600314 002DE 60000970000292600314533030324445
/dev/sdr 000292600314 002DF 60000970000292600314533030324446
/dev/sds 000292600314 002E0 60000970000292600314533030324530
/dev/sdt 000292600314 002E1 60000970000292600314533030324531
/dev/sdu 000292600314 002E2 60000970000292600314533030324532
/dev/sdv 000292600314 002E3 60000970000292600314533030324533
/dev/sdw 000292600314 002E4 60000970000292600314533030324534
/dev/sdx 000292600314 00219 60000970000292600314533030323139
/dev/sdy 000292600314 0021A 60000970000292600314533030323141
/dev/sdz 000292600314 0021B 60000970000292600314533030323142
/dev/dm-6 000292600314 0002C 60000970000292600314533030303243
/dev/dm-7 000292600314 002DC 60000970000292600314533030324443
/dev/dm-8 000292600314 002DD 60000970000292600314533030324444
/dev/dm-9 000292600314 002DE 60000970000292600314533030324445
/dev/sdaa 000292600314 0011D 60000970000292600314533030313144
/dev/sdab 000292600314 0011E 60000970000292600314533030313145
/dev/sdac 000292600314 0011F 60000970000292600314533030313146
/dev/sdad 000292600314 00167 60000970000292600314533030313637
/dev/sdae 000292600314 0017E 60000970000292600314533030313745
/dev/sdaf 000292600314 001AD 60000970000292600314533030314144
/dev/sdag 000292600314 001F0 60000970000292600314533030314630
/dev/sdah 000292600314 0011D 60000970000292600314533030313144
/dev/sdai 000292600314 0011E 60000970000292600314533030313145
/dev/sdaj 000292600314 0011F 60000970000292600314533030313146
/dev/sdak 000292600314 00167 60000970000292600314533030313637
/dev/sdal 000292600314 0017E 60000970000292600314533030313745
/dev/sdam 000292600314 001AD 60000970000292600314533030314144
/dev/sdan 000292600314 001F0 60000970000292600314533030314630
/dev/dm-10 000292600314 002DF 60000970000292600314533030324446
/dev/dm-11 000292600314 002E0 60000970000292600314533030324530
/dev/dm-12 000292600314 002E1 60000970000292600314533030324531
/dev/dm-13 000292600314 002E2 60000970000292600314533030324532
/dev/dm-14 000292600314 002E3 60000970000292600314533030324533
/dev/dm-15 000292600314 002E4 60000970000292600314533030324534
/dev/dm-16 000292600314 00219 60000970000292600314533030323139
/dev/dm-17 000292600314 0021A 60000970000292600314533030323141
/dev/dm-18 000292600314 0021B 60000970000292600314533030323142
/dev/dm-19 000292600314 002DF 60000970000292600314533030324446
/dev/dm-20 000292600314 002DF 60000970000292600314533030324446
/dev/dm-21 000292600314 002E0 60000970000292600314533030324530
/dev/dm-22 000292600314 002E1 60000970000292600314533030324531
/dev/dm-23 000292600314 002E2 60000970000292600314533030324532
/dev/dm-24 000292600314 002E3 60000970000292600314533030324533
/dev/dm-25 000292600314 002E4 60000970000292600314533030324534
/dev/dm-26 000292600314 00219 60000970000292600314533030323139
/dev/dm-27 000292600314 0021A 60000970000292600314533030323141
/dev/dm-28 000292600314 0021B 60000970000292600314533030323142
/dev/raw/raw20 000292600314 002DF 60000970000292600314533030324446
/dev/raw/raw21 000292600314 002DF 60000970000292600314533030324446
/dev/raw/raw22 000292600314 002E0 60000970000292600314533030324530
/dev/raw/raw23 000292600314 002E1 60000970000292600314533030324531
/dev/raw/raw24 000292600314 002E2 60000970000292600314533030324532
/dev/raw/raw25 000292600314 002E3 60000970000292600314533030324533
/dev/raw/raw26 000292600314 002E4 60000970000292600314533030324534
/dev/raw/raw27 000292600314 00219 60000970000292600314533030323139
/dev/raw/raw28 000292600314 0021A 60000970000292600314533030323141

Phase – 2 : Detecting New LUNS

Scanning new LUN disks allocated from the same existing storage device

[root@gurkulindia-linuxserver>> /dev/raw]#for hba in /sys/class/scsi_host/host?
>do
>echo “Scanning for new devices on hba $hba…”
>echo ‘- – -‘ >$hba/scan
>done
Scanning for new devices on hba /sys/class/scsi_host/host0…
Scanning for new devices on hba /sys/class/scsi_host/host1…

Run INQ utility to check the new devices recognised by above command

Note:  New Devices with the newly allocated LUN numbers are underlined in the below output

[root@gurkulindia-linuxserver>> /dev/raw]# /emc-tools/inq.linux -sym_wwn -no_dots
Inquiry utility, Version V7.3-883 (Rev 1.0) (SIL Version V6.5.1.0 (Edit Level 883)
Copyright (C) by EMC Corporation, all rights reserved.
For help type inq -h.
————————————————————————-
Symmetrix DeviceSymm Serial # Device # WWN
————————————————————————-
/dev/sda 000292600314 0002C 60000970000292600314533030303243
/dev/sdb 000292600314 002DC 60000970000292600314533030324443
/dev/sdc 000292600314 002DD 60000970000292600314533030324444
/dev/sdd 000292600314 002DE 60000970000292600314533030324445
/dev/sde 000292600314 002DF 60000970000292600314533030324446
/dev/sdf 000292600314 002E0 60000970000292600314533030324530
/dev/sdg 000292600314 002E1 60000970000292600314533030324531
/dev/sdh 000292600314 002E2 60000970000292600314533030324532
/dev/sdi 000292600314 002E3 60000970000292600314533030324533
/dev/sdj 000292600314 002E4 60000970000292600314533030324534
/dev/sdk 000292600314 00219 60000970000292600314533030323139
/dev/sdl 000292600314 0021A 60000970000292600314533030323141
/dev/sdm 000292600314 0021B 60000970000292600314533030323142
/dev/sdn 000292600314 0002C 60000970000292600314533030303243
/dev/sdo 000292600314 002DC 60000970000292600314533030324443
/dev/sdp 000292600314 002DD 60000970000292600314533030324444
/dev/sdq 000292600314 002DE 60000970000292600314533030324445
/dev/sdr 000292600314 002DF 60000970000292600314533030324446
/dev/sds 000292600314 002E0 60000970000292600314533030324530
/dev/sdt 000292600314 002E1 60000970000292600314533030324531
/dev/sdu 000292600314 002E2 60000970000292600314533030324532
/dev/sdv 000292600314 002E3 60000970000292600314533030324533
/dev/sdw 000292600314 002E4 60000970000292600314533030324534
/dev/sdx 000292600314 00219 60000970000292600314533030323139
/dev/sdy 000292600314 0021A 60000970000292600314533030323141
/dev/sdz 000292600314 0021B 60000970000292600314533030323142
/dev/dm-6 000292600314 0002C 60000970000292600314533030303243
/dev/dm-7 000292600314 002DC 60000970000292600314533030324443
/dev/dm-8 000292600314 002DD 60000970000292600314533030324444
/dev/dm-9 000292600314 002DE 60000970000292600314533030324445
/dev/sdaa 000292600314 0011D 60000970000292600314533030313144
/dev/sdab 000292600314 0011E 60000970000292600314533030313145
/dev/sdac 000292600314 0011F 60000970000292600314533030313146
/dev/sdad 000292600314 00167 60000970000292600314533030313637
/dev/sdae 000292600314 0017E 60000970000292600314533030313745
/dev/sdaf 000292600314 001AD 60000970000292600314533030314144
/dev/sdag 000292600314 001F0 60000970000292600314533030314630
/dev/sdah 000292600314 0011D 60000970000292600314533030313144
/dev/sdai 000292600314 0011E 60000970000292600314533030313145
/dev/sdaj 000292600314 0011F 60000970000292600314533030313146
/dev/sdak 000292600314 00167 60000970000292600314533030313637
/dev/sdal 000292600314 0017E 60000970000292600314533030313745
/dev/sdam 000292600314 001AD 60000970000292600314533030314144
/dev/sdan 000292600314 001F0 60000970000292600314533030314630
/dev/dm-10 000292600314 002DF 60000970000292600314533030324446
/dev/dm-11 000292600314 002E0 60000970000292600314533030324530
/dev/dm-12 000292600314 002E1 60000970000292600314533030324531
/dev/dm-13 000292600314 002E2 60000970000292600314533030324532
/dev/dm-14 000292600314 002E3 60000970000292600314533030324533
/dev/dm-15 000292600314 002E4 60000970000292600314533030324534
/dev/dm-16 000292600314 00219 60000970000292600314533030323139
/dev/dm-17 000292600314 0021A 60000970000292600314533030323141
/dev/dm-18 000292600314 0021B 60000970000292600314533030323142
/dev/dm-19 000292600314 002DF 60000970000292600314533030324446
/dev/dm-20 000292600314 002DF 60000970000292600314533030324446
/dev/dm-21 000292600314 002E0 60000970000292600314533030324530
/dev/dm-22 000292600314 002E1 60000970000292600314533030324531
/dev/dm-23 000292600314 002E2 60000970000292600314533030324532
/dev/dm-24 000292600314 002E3 60000970000292600314533030324533
/dev/dm-25 000292600314 002E4 60000970000292600314533030324534
/dev/dm-26 000292600314 00219 60000970000292600314533030323139
/dev/dm-27 000292600314 0021A 60000970000292600314533030323141
/dev/dm-28 000292600314 0021B 60000970000292600314533030323142
/dev/dm-32 000292600314 0011D 60000970000292600314533030313144  
/dev/dm-33 000292600314 0011E 60000970000292600314533030313145
/dev/dm-34 000292600314 0011F 60000970000292600314533030313146

/dev/dm-35 000292600314 00167 60000970000292600314533030313637

/dev/dm-36 000292600314 0017E 60000970000292600314533030313745
/dev/dm-37 000292600314 001AD 60000970000292600314533030314144
/dev/dm-38 000292600314 001F0 60000970000292600314533030314630
/dev/raw/raw20 000292600314 002DF 60000970000292600314533030324446
/dev/raw/raw21 000292600314 002DF 60000970000292600314533030324446
/dev/raw/raw22 000292600314 002E0 60000970000292600314533030324530
/dev/raw/raw23 000292600314 002E1 60000970000292600314533030324531
/dev/raw/raw24 000292600314 002E2 60000970000292600314533030324532
/dev/raw/raw25 000292600314 002E3 60000970000292600314533030324533
/dev/raw/raw26 000292600314 002E4 60000970000292600314533030324534
/dev/raw/raw27 000292600314 00219 60000970000292600314533030323139
/dev/raw/raw28 000292600314 0021A 60000970000292600314533030323141
/dev/raw/raw29 000292600314 0021B 60000970000292600314533030323142

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# /emc-tools/inq.linux -sym_wwn -no_dots | egrep “011D|011E|011F|0167|017E|01AD|01F0”
/dev/sdaa 000292600314 0011D 60000970000292600314533030313144
/dev/sdab 000292600314 0011E 60000970000292600314533030313145
/dev/sdac 000292600314 0011F 60000970000292600314533030313146
/dev/sdad 000292600314 00167 60000970000292600314533030313637
/dev/sdae 000292600314 0017E 60000970000292600314533030313745
/dev/sdaf 000292600314 001AD 60000970000292600314533030314144
/dev/sdag 000292600314 001F0 60000970000292600314533030314630
/dev/sdah 000292600314 0011D 60000970000292600314533030313144
/dev/sdai 000292600314 0011E 60000970000292600314533030313145
/dev/sdaj 000292600314 0011F 60000970000292600314533030313146
/dev/sdak 000292600314 00167 60000970000292600314533030313637
/dev/sdal 000292600314 0017E 60000970000292600314533030313745
/dev/sdam 000292600314 001AD 60000970000292600314533030314144
/dev/sdan 000292600314 001F0 60000970000292600314533030314630
/dev/dm-32 000292600314 0011D 60000970000292600314533030313144    <– New Volumes are underlined
/dev/dm-33 000292600314 0011E 60000970000292600314533030313145
/dev/dm-34 000292600314 0011F 60000970000292600314533030313146
/dev/dm-35 000292600314 00167 60000970000292600314533030313637
/dev/dm-36 000292600314 0017E 60000970000292600314533030313745
/dev/dm-38 000292600314 001F0 60000970000292600314533030314630

Creating Physical Volumes using the new Storage LUNS we detected from above

( New Devices are  /dev/db-32, /dev/db-33, /dev/db-34, /dev/db-35, /dev/db-36, /dev/db-38 )

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvcreate /dev/dm-32
Physical volume “/dev/dm-32” successfully created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvcreate /dev/dm-33
Physical volume “/dev/dm-33” successfully created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvcreate /dev/dm-34
Physical volume “/dev/dm-34” successfully created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvcreate /dev/dm-35
Physical volume “/dev/dm-35” successfully created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvcreate /dev/dm-36
Physical volume “/dev/dm-36” successfully created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvcreate /dev/dm-38
Physical volume “/dev/dm-38” successfully created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgextend sybasevg /dev/dm-32
Volume group “sybasevg” successfully extended

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgextend sybasevg /dev/dm-33
Volume group “sybasevg” successfully extended

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgextend sybasevg /dev/dm-34
Volume group “sybasevg” successfully extended

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgextend sybasevg /dev/dm-35
Volume group “sybasevg” successfully extended

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgextend sybasevg /dev/dm-36
Volume group “sybasevg” successfully extended

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# vgextend sybasevg /dev/dm-38
Volume group “sybasevg” successfully extended

From the below “PVS” command you can see new physical volumes that we created using above “pvcreate ” and added to the sybasevg using “vgextend” command

Note: Please note that the actual size and free space available in each Physical volume

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvs
PV VG Fmt Attr PSize PFree
/dev/cciss/c0d0p2 rootvg lvm2 a- 136.56G 0
/dev/dm-10 sybasevg lvm2 a- 1020.00M 0
/dev/dm-11 sybasevg lvm2 a- 30.00G 0
/dev/dm-12 sybasevg lvm2 a- 30.00G 624.00M
/dev/dm-13 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-14 sybasevg lvm2 a- 10.00G 240.00M
/dev/dm-15 sybasevg lvm2 a- 20.00G 476.00M
/dev/dm-16 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-17 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-18 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-32 sybasevg lvm2 a- 29.29G 29.29G
/dev/dm-33 sybasevg lvm2 a- 29.29G 29.29G
/dev/dm-34 sybasevg lvm2 a- 29.29G 29.29G
/dev/dm-35 sybasevg lvm2 a- 500.00M 500.00M
/dev/dm-36 sybasevg lvm2 a- 11.71G 11.71G
/dev/dm-38 sybasevg lvm2 a- 296.00M 296.00M
/dev/dm-7 sybasefsdg lvm2 a- 8.00G 0
/dev/dm-8 sybasefsdg lvm2 a- 6.00G 0
/dev/dm-9 sybasefsdg lvm2 a- 40.00G 0

From below output you can notice that create PV and adding them to VG doesn’t actually create any new Logical Volumes. In the next command we will be creating new logical volumes ( sybase raw volumes) using the lvcreate command

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data01-old-vol sybasevg -wi-ao 29.30G
data02-old-vol sybasevg -wi-ao 29.30G
data03-old-vol sybasevg -wi-ao 29.30G
data04-old-vol sybasevg -wi-ao 9.77G
data05-old-vol sybasevg -wi-ao 29.30G
data06-old-vol sybasevg -wi-ao 29.30G
data07-old-vol sybasevg -wi-ao 29.30G
log01-old-vol sybasevg -wi-ao 19.53G
master_old_vol sybasevg -wi-ao 300.00M
procs_old_vol sybasevg -wi-ao 720.00M

lvcreate sytax:

# lvcreate -l -n

Importanat Notes – 1 : In normal cases we will allow LVM to pick any of the available physical volumes to create the logical volume of given size. In that case one logical volume may spread more than one physical volume, or one physical volume may consists more than one logical volume.

Important Notes – 2: Whenever sybase request for raw-volumes they will ask System Admins to change the ownership of the raw volumes to “sybase” user, so that sybase DB can directly access the volume for it’s operation.

Important Notes-3: In this case, we have requested the each storage Lun, with exactly same size as that sybase DB want to use for each raw volume. And we are creating Logical Volume by exclusively specifying the physical volume we want to use for the Logical volume, so that the corresponding raw devices will be easy to manage .

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -l 7499 -n data01-new-rawvol sybasevg /dev/dm-32

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
data01-new-rawvol sybasevg -wi-a- 29.30G
data01-old-vol sybasevg -wi-ao 29.30G
data02-old-vol sybasevg -wi-ao 29.30G
data03-old-vol sybasevg -wi-ao 29.30G
data04-old-vol sybasevg -wi-ao 9.77G
data05-old-vol sybasevg -wi-ao 29.30G
data06-old-vol sybasevg -wi-ao 29.30G
data07-old-vol sybasevg -wi-ao 29.30G
log01-old-vol sybasevg -wi-ao 19.53G
master_old_vol sybasevg -wi-ao 300.00M
procs_old_vol sybasevg -wi-ao 720.00M
[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvs
PV VG Fmt Attr PSize PFree
/dev/cciss/c0d0p2 rootvg lvm2 a- 136.56G 0
/dev/dm-10 sybasevg lvm2 a- 1020.0 0M 0
/dev/dm-11 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-12 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-13 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-14 sybasevg lvm2 a- 10.00G 240.00M
/dev/dm-15 sybasevg lvm2 a- 20.00G 476.00M
/dev/dm-16 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-17 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-18 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-32 sybasevg lvm2 a- 29.29G 0                <– New Volumes are underlined
/dev/dm-33 sybasevg lvm2 a- 29.29G 29.29G
/dev/dm-34 sybasevg lvm2 a- 29.29G 29.29G
/dev/dm-35 sybasevg lvm2 a- 500.00M 500.00M

/dev/dm-36 sybasevg lvm2 a- 11.71G 11.71G
/dev/dm-38 sybasevg lvm2 a- 296.00M 296.00M
/dev/dm-7 sybasefsdg lvm2 a- 8.00G 0
/dev/dm-8 sybasefsdg lvm2 a- 6.00G 0
/dev/dm-9 sybasefsdg lvm2 a- 40.00G 0

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -l 7499 -n data02-new-rawvol sybasevg /dev/dm-33
Logical volume “data02-new-rawvol ” created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -l 7499 -n data03-new-rawvol sybasevg /dev/dm-34
Logical volume “data03-new-rawvol ” created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -L 500M -n procs-new-rawvol sybasevg /dev/dm-35
Logical volume “procs-new-rawvol ” created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -L 12000M -n logs01-new-rawvol sybasevg /dev/dm-36
Insufficient free space: 3000 extents needed, but only 2999 available

Note: Above Command was failed because, initially we were in the impression that LVM can see the same size for each new Lun, whatever was allocated by storage, but the fact is LVM looks at storage interms of Pysical extents ( Chunks of data blocks on physical volume) so it will see minor difference than what storage allocation made. In th next command we have user -l option to create volume using all available extents of the disk .

You can check free PE information using #pvdislay

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -l 2999 -n logs01-new-rawvol sybasevg /dev/dm-36
Logical volume “logs01-new-rawvol ” created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -L 300M -n master-new-rawvol sybasevg /dev/dm-38
Insufficient free space: 75 extents needed, but only 74 available

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvcreate -l 74 -n master-new-rawvol sybasevg /dev/dm-38
Logical volume “master-new-rawvol ” created

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# pvs
PV VG Fmt Attr PSize PFree
/dev/cciss/c0d0p2 rootvg lvm2 a- 136.56G 0
/dev/dm-10 sybasevg lvm2 a- 1020.00M 0
/dev/dm-11 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-12 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-13 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-14 sybasevg lvm2 a- 10.00G 240.00M
/dev/dm-15 sybasevg lvm2 a- 20.00G 476.00M
/dev/dm-16 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-17 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-18 sybasevg lvm2 a- 30.00G 720.00M
/dev/dm-32 sybasevg lvm2 a- 29.29G 0
/dev/dm-33 sybasevg lvm2 a- 29.29G 0
/dev/dm-34 sybasevg lvm2 a- 29.29G 0
/dev/dm-35 sybasevg lvm2 a- 500.00M 0
/dev/dm-36 sybasevg lvm2 a- 11.71G 0
/dev/dm-38 sybasevg lvm2 a- 296.00M 0
/dev/dm-7 sybasefsdg lvm2 a- 8.00G 0
/dev/dm-8 sybasefsdg lvm2 a- 6.00G 0
/dev/dm-9 sybasefsdg lvm2 a- 40.00G 0
[root@gurkulindia-linuxserver>> /dev/raw-mapper]# lvs
LV VG Attr LSize Origin Snap% Move Log Copy% Convert
kdumpvol rootvg -wi-ao 23.59G
rootvol rootvg -wi-ao 4.00G
sbclocalvol rootvg -wi-ao 93.97G
swapvol rootvg -wi-ao 8.00G
tmpvol rootvg -wi-ao 3.00G
varvol rootvg -wi-ao 4.00G
sybaseapp sybasefsdg -wi-ao 8.00G
sybasedump sybasefsdg -wi-ao 47.99G
tempdb sybasefsdg -wi-ao 6.00G
data01-new-rawvol sybasevg -wi-a- 29.29G  <– New Volumes are underlined
data02-new-rawvol sybasevg -wi-a- 29.29G
data03-new-rawvol sybasevg -wi-a- 29.29G
logs01-new-rawvol sybasevg -wi-a- 11.71G
master-new-rawvol sybasevg -wi-a- 296.00M
procs-new-rawvol sybasevg -wi-a- 500.00M
data01-old-vol sybasevg -wi-ao 29.30G
data02-old-vol sybasevg -wi-ao 29.30G
data03-old-vol sybasevg -wi-ao 29.30G
data04-old-vol sybasevg -wi-ao 9.77G
data05-old-vol sybasevg -wi-ao 29.30G
data06-old-vol sybasevg -wi-ao 29.30G
data07-old-vol sybasevg -wi-ao 29.30G
log01-old-vol sybasevg -wi-ao 19.53G
master_old_vol sybasevg -wi-ao 300.00M
procs_old_vol sybasevg -wi-ao 720.00M

Look at the raw device files ( these are link files) of new volumes, under the /dev/raw-mapper

[root@gurkulindia-linuxserver>> /dev/raw-mapper]# cd /dev/raw-mapper/
[root@gurkulindia-linuxserver>> /dev/raw-mapper]# ls -rlt
total 0
lrwxrwxrwx 1 root root 12 Jul 23 17:11 logs01-old-vol -> ../raw/raw26
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data02-old-vol -> ../raw/raw23
lrwxrwxrwx 1 root root 12 Jul 23 17:11 procs_old_vol -> ../raw/raw21
lrwxrwxrwx 1 root root 12 Jul 23 17:11 master_old_vol -> ../raw/raw20
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data04-old-vol -> ../raw/raw25
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data03-old-vol -> ../raw/raw24
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data06-old-vol -> ../raw/raw28
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data01-old-vol -> ../raw/raw22
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data05-old-vol -> ../raw/raw27
lrwxrwxrwx 1 root root 12 Jul 23 17:11 data07-old-vol -> ../raw/raw29
lrwxrwxrwx 1 root root 12 Sep 20 20:07 data01-new-rawvol -> ../raw/raw42
lrwxrwxrwx 1 root root 12 Sep 20 22:23 data02-new-rawvol -> ../raw/raw40
lrwxrwxrwx 1 root root 12 Sep 20 22:23 data03-new-rawvol -> ../raw/raw41
lrwxrwxrwx 1 root root 12 Sep 20 22:28 procs-new-rawvol -> ../raw/raw43
lrwxrwxrwx 1 root root 12 Sep 20 22:29 logs01-new-rawvol -> ../raw/raw44
lrwxrwxrwx 1 root root 12 Sep 20 22:29 master-new-rawvol -> ../raw/raw45

Look at the raw device files ( actual files) of new volumes, under the /dev/raw, check the permissions. These files should be owned by sybase. If not already set, just set with the chown command.

[root@gurkulindia-linuxserver>> /dev/raw]# ls -lrt /dev/raw
total 0
crw-rw—- 1 sybase sybase 162, 25 Jul 23 17:11 raw25
crw-rw—- 1 sybase sybase 162, 24 Jul 23 17:11 raw24
crw-rw—- 1 sybase sybase 162, 27 Jul 23 17:11 raw27
crw-rw—- 1 sybase sybase 162, 42 Sep 20 20:07 raw42
crw-rw—- 1 sybase sybase 162, 40 Sep 20 22:23 raw40
crw-rw—- 1 sybase sybase 162, 41 Sep 20 22:23 raw41
crw-rw—- 1 sybase sybase 162, 43 Sep 20 22:28 raw43
crw-rw—- 1 sybase sybase 162, 44 Sep 20 22:29 raw44
crw-rw—- 1 sybase sybase 162, 45 Sep 20 22:29 raw45
crw-rw—- 1 sybase sybase 162, 28 Sep 20 22:32 raw28
crw-rw—- 1 sybase sybase 162, 29 Sep 20 22:32 raw29
crw-rw—- 1 sybase sybase 162, 21 Sep 20 22:32 raw21
crw-rw—- 1 sybase sybase 162, 22 Sep 20 22:33 raw22
crw-rw—- 1 sybase sybase 162, 20 Sep 20 22:33 raw20
crw-rw—- 1 sybase sybase 162, 23 Sep 20 22:33 raw23
crw-rw—- 1 sybase sybase 162, 26 Sep 20 22:33 raw26

Finally you just have to mail the below informarmation to sybase team about the new raw-volume informarmation:

data01-new-rawvol -> ../raw/raw42
data02-new-rawvol -> ../raw/raw40
data03-new-rawvol -> ../raw/raw41
procs-new-rawvol -> ../raw/raw43
logs01-new-rawvol -> ../raw/raw44
master-new-rawvol -> ../raw/raw45

Ramdev

Ramdev

I have started unixadminschool.com ( aka gurkulindia.com) in 2009 as my own personal reference blog, and later sometime i have realized that my leanings might be helpful for other unixadmins if I manage my knowledge-base in more user friendly format. And the result is today's' unixadminschool.com. You can connect me at - https://www.linkedin.com/in/unixadminschool/

7 Responses

  1. Chaitanya says:

    look good …this will be very help full for us to understand the process of adding with out any reboot

  2. Ramdev says:

    @Chitanya – True. The ability to perform storage operations without downtime takes the system admins to the next level towards the perfectness.
    Thanks for visiting the post

  3. shekar says:

    Ram : Sorry my question may be wrong .What i need to know is , current status say using powermt display dev=all ,say i can ee 2 path , now SAN team have moved to diff SAN array ,dded 2 more path /port s at the SAN array as ( reduntancy ) .After redudant /path have been addess ,. What is command in Linux 4.x i need to run to get these 4 paths at the Linux Server side. when i use powermt display dev=all .pl

  4. madhu says:

    great job, thank u for spending ur valuable time for sharing all these information,really excellent

  5. madhu says:

    thank u for spending ur valuable time for sharing all these information,really excellent

  1. May 22, 2014

    […] Additional Reference  to work with Linux Storage with Multipath-  San Storage Migration in Linux […]

  2. September 18, 2015

    […] Read – Online configuration of new SAN disks to create new sybase raw volumes, using LVM. […]

What is in your mind, about this post ? Leave a Reply

Close
  Our next learning article is ready, subscribe it in your email

What is your Learning Goal for Next Six Months ? Talk to us