Adding extra volume group » История » Версия 2
Dmitry Chernyak, 16.12.2016 00:38
| 1 | 1 | Dmitry Chernyak | h1. Adding extra volume group |
|---|---|---|---|
| 2 | 1 | Dmitry Chernyak | |
| 3 | 1 | Dmitry Chernyak | If your server has two types of disks, for example 2xSATA + 8xSAS, then you need to initialize the second VG and (if needed) to make it as a main for creating of virtual machimes: |
| 4 | 1 | Dmitry Chernyak | |
| 5 | 1 | Dmitry Chernyak | This operations should be done on both nodes: |
| 6 | 1 | Dmitry Chernyak | Partition disks: |
| 7 | 1 | Dmitry Chernyak | <pre> |
| 8 | 1 | Dmitry Chernyak | fdisk /dev/sdc |
| 9 | 1 | Dmitry Chernyak | </pre> |
| 10 | 1 | Dmitry Chernyak | make a primary partition on whole disk |
| 11 | 1 | Dmitry Chernyak | |
| 12 | 1 | Dmitry Chernyak | If you use Software RAID, then copy this prtitioning to all the disks (be careful, don't mix up the disks): |
| 13 | 1 | Dmitry Chernyak | <pre> |
| 14 | 1 | Dmitry Chernyak | for i in d e f g h i j; do sfdisk -d /dev/sdc|sfdisk /dev/sd$i; done |
| 15 | 1 | Dmitry Chernyak | </pre> |
| 16 | 1 | Dmitry Chernyak | |
| 17 | 2 | Dmitry Chernyak | Initialize md, vg (skip mdadm command if you have hardware RAID) |
| 18 | 1 | Dmitry Chernyak | <pre> |
| 19 | 1 | Dmitry Chernyak | mdadm --create -n8 -l10 /dev/md3 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1 /dev/sdh1 /dev/sdi1 /dev/sdj1 |
| 20 | 1 | Dmitry Chernyak | pvcreate /dev/md3 |
| 21 | 1 | Dmitry Chernyak | vgcreate sas /dev/md3 |
| 22 | 1 | Dmitry Chernyak | </pre> |
| 23 | 1 | Dmitry Chernyak | |
| 24 | 1 | Dmitry Chernyak | And, finally, tune the cluster defaults to use the new vg (issue this one time on the master node): |
| 25 | 1 | Dmitry Chernyak | <pre> |
| 26 | 1 | Dmitry Chernyak | gnt-cluster modify --vg-name=sas --disk-parameters=drbd:metavg=sas |
| 27 | 1 | Dmitry Chernyak | </pre> |
| 28 | 1 | Dmitry Chernyak | |
| 29 | 1 | Dmitry Chernyak | By default all disks have set the deadline scheduler. |
| 30 | 1 | Dmitry Chernyak | If you use the hardware RAID or separate external storage, connected via FC/Infiniband/iSCSI, then, POSSIBLE, will be better to use noop scheduler for the underlying physical disks. |
| 31 | 1 | Dmitry Chernyak | Nevertheless, the deadline scheduler will be sufficient for all disk types. |
| 32 | 1 | Dmitry Chernyak | |
| 33 | 1 | Dmitry Chernyak | The article about comparing the three variants of offset in raid10 (SCI use the default one, NEAR): |
| 34 | 1 | Dmitry Chernyak | http://www.ilsistemista.net/index.php/linux-a-unix/35-linux-software-raid-10-layouts-performance-near-far-and-offset-benchmark-analysis.html?start=1 |