Sistem production ortamina alindiktan bir sure sonra diskler uzerinde buyuyen veri ihtiyacini karsilamak icin, kullanilan disk alanlarini genisletmek gerekebilir. Fakat bu is her zaman cok kolay olmaz. Cunku, belirli bir zaman once yapilmis olan "sizing" calismalari, is sureclerinin ihtiyaclarini karsilayamaz duruma gelebilir ve vakti zamaninda tanimlanmis olan disk boyutlarini genisletme ihtiyaci ortaya cikar. Bu asamada Storage ve isletim sistemi katmaninda eszamanli olarak planli bir calisma yapmak gerekir. Kritik nokta bu calismalarin online yapilmasi gerektigidir. Zira artik sistemimiz gelistirme ve/veya test ortami olmaktan cikmis ve artik uzerinde son kullanicinin calistigi bir uretim (production) ortami haline gelmistir.
Neyse ki, EF560 ve Linux urunlerini birlikte kullanan ortamlar, bu isi bir dizi iyi tanimlanmis adim ile gerceklestirebilir. Baslamadan once, bu yaziyi yazarken kullandigim Linux dagitimi ve kernel versiyonunu paylasacagim. Zira bu yazida kullanilan yontemler, kernel versiyonlari ve farkli dagitimlar arasinda bazi degisiklikler gosterebiliyor. Asagidaki komut satiri ciktisindan da gorulecegi uzere, Demo sunucusu uzerinde Oracle Redhat Linux 6.6 ve Kernel surumu olarak 3.8.13 kurulu. device-mapper-multipath yazilimi icin herhangi bir guncelleme yapmadim. Surum ile birlikte gelen multipath versiyonunu kullaniyorum.
[root@tslnx01 ~]# uname -a
Linux tslnx01 3.8.13-44.1.1.el6uek.x86_64 #2 SMP Wed Sep 10 06:10:25 PDT 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@tslnx01 ~]# cat /etc/oracle-release
Oracle Linux Server release 6.6
[root@tslnx01 ~]# rpm -qa | grep -i device-mapper-multipath
device-mapper-multipath-libs-0.4.9-80.0.1.el6.x86_64
device-mapper-multipath-0.4.9-80.0.1.el6.x86_64Oncelikle, daha fazla yer ihtiyaci duyulan disk alani icin karsilik gelen LUN boyutlari storage tarafinda yeniden boyutlandirilmalidir. Bunu icin SANtricity yazilimi kullanilabilir. Asagidaki sema dan gorulecegi uzere -Storage and Copy Services- penceresi icerisinde ilgili LUN bulunarak yeniden boyutlandirilir.
Bundan sonraki islemler, isletim sistemi tarafinda yapilir. Storage tarafinda 30Gb olarak genisletilen LUN, linux isletim sisteminde halen 20Gb olarak goruluyor.
[root@tslnx01 dev]# multipath -ll
mpathr (360080e50004316c8000000ea55a34223) dm-3 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:3 sde 8:64 active ready running
`- 2:0:0:3 sdm 8:192 active ready running
mpathq (360080e500029b50c0000012555a3420b) dm-2 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:2 sdd 8:48 active ready running
`- 2:0:0:2 sdl 8:176 active ready running
mpathp (360080e50004316c8000000e955a34204) dm-1 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:1 sdc 8:32 active ready running
`- 2:0:0:1 sdk 8:160 active ready running
mpatho (360080e500029b50c0000012155a341ed) dm-0 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:0 sdb 8:16 active ready running
`- 2:0:0:0 sdj 8:144 active ready running
mpathv (360080e50004316c8000001d655b8432e) dm-7 NETAPP,INF-01-00
size=20G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:8 sdi 8:128 active ready running
`- 2:0:0:8 sdq 65:0 active ready running
mpathu (360080e500029b50c0000021155b84318) dm-6 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:6 sdh 8:112 active ready running
`- 2:0:0:6 sdp 8:240 active ready running
mpatht (360080e500029b50c0000021055b842f0) dm-4 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:4 sdf 8:80 active ready running
`- 2:0:0:4 sdn 8:208 active ready running
mpaths (360080e50004316c8000001d555b8430e) dm-5 NETAPP,INF-01-00
size=10G features='0' hwhandler='0' wp=rw
`-+- policy='round-robin 0' prio=1 status=active
|- 1:0:0:5 sdg 8:96 active ready running
`- 2:0:0:5 sdo 8:224 active ready running
[root@tslnx01 dev]# fdisk -l /dev/mapper/mpathv
Disk /dev/mapper/mpathv: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x6f048ad4
[root@tslnx01 dev]# fdisk -l /dev/dm-7
Disk /dev/dm-7: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x6f048ad4multipath -ll komutu ile genisletilmis olan multipath device'in bagli oldugu scsi disk'leri bulabilirsiniz. Daha sonra bu scsi disk'ler icin rescan islemi yapilmasi, boylece scsi disk'lerin yeni LUN boyutunu algilamasi saglanir.
[root@tslnx01 dev]# echo 1 > /sys/block/sdi/device/rescan
[root@tslnx01 dev]# echo 1 > /sys/block/sdq/device/rescan
[root@tslnx01 dev]# fdisk -l /dev/sdi
Disk /dev/sdi: 32.2 GB, 32212254720 bytes
64 heads, 32 sectors/track, 30720 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x6f048ad4
[root@tslnx01 dev]# fdisk -l /dev/sdq
Disk /dev/sdq: 32.2 GB, 32212254720 bytes
64 heads, 32 sectors/track, 30720 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x6f048ad4
[root@tslnx01 dev]#Yeni LUN boyutlari scsi diskler tarafindan guncellenmesini sagladik. Fakat multipath yazilimindan da bu iki disk'i map olarak kullanan /dev/dm-7 ve /dev/mapper/mpathv map'ininde guncellenmesi gerekir. Bunun icin asagidaki komut calistirilir;
[root@tslnx01 dev]# multipathd -k'resize map mpathv'
ok
[root@tslnx01 dev]# fdisk -l /dev/dm-7
Disk /dev/dm-7: 32.2 GB, 32212254720 bytes
255 heads, 63 sectors/track, 3916 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x6f048ad4
[root@tslnx01 dev]# Bundan sonra yapilmasi gerekenler, hangi mantiksal katman ile disk erisimiyapildigi ile ilgili. Eger Oracle ASM kullaniliyor ise diskler ASM tarafinda yeniden boyutlandirilmali. Eger disklere LVM katmani ile erisiliyor ise bu durumda LVM ile Physical Volume yeniden boyutlandirilir ve Logical Volume genisletirilir. Eger diskler dogrudan formatlanarak mount edildi ise, bu durumda mount point dogrudan yeniden boyutlandirilir.
Logical katmanda yapilmasi gerekenler ileriki kayitlarda detayli bir sekilde anlatilacaktir.
Comments