GFS2 Cluster in VMware

From Linux NFS

You do not have permission to edit this page, for the following reason:

You can view and copy the source of this page:

==VMware== * bought a copy of VMware Workstation 6, installed it on my T-43 Thinkpad <tt>"atro"</tt>(running openSuSE 10.2, 2GB of RAM). * made a new virtual machine: '''OS''': Linux, '''Version''': "Other Linux 2.6.x kernel", '''Networking''': Bridged, '''Disk''': 4GB, split into 2GB files, '''RAM''': 256MB * installed Fedora 8 in it -- even X worked well with only 256MB of RAM(!) -- guest is named <tt>"guest1"</tt> * yum-installed '''gfs2-utils''' and '''libvolume_id-devel''' ''(i also tried cman, cman-devel, openais, openais-devel, and lvm2-cluster, but even '''they''' were out-of-date with the stock Fedora kernel, and so are also too old for the pNFS kernels)'' * downloaded and installed '''device-mapper-1.02.22''', '''openais-0.80.3''', '''cluster-2.01.00''', and '''lvm2-2.02.28''' ==ATA over Ethernet (for guest cluster shared storage)== * yum-installed AoE initiator (client) '''aoetools-18-1''' on <tt>guest1</tt> * downloaded AoE target (server) [http://internap.dl.sourceforge.net/sourceforge/aoetools/vblade-15.tgz vblade-15.tgz] and installed it on <tt>atro</tt> * i set aside a spare partition on <tt>atro</tt> to export as a block device over AoE: ** <tt>[atro] $ sudo ln -s /dev/sda6 /dev/AoE</tt> ** <tt>[atro] $ sudo vbladed 0 1 eth0 /dev/AoE</tt> ''(major dev num 0, minor 1)'' ** <tt>[guest1] $ sudo modprobe aoe</tt> *** .. AoE discovers all exported devices on the LAN; mine was the only one, and immediately appeared as <tt>/dev/etherd/e0.1</tt>. Mounting it "just worked"; props to AoE! ==LVM and GFS2 setup== * prep physical volume for LVM: ** <tt>[guest1] $ sudo pvcreate -M 2 /dev/etherd/e0.1</tt> * create the volume group '''GuestVolGroup''' and add all of the AoE "device" to it: ** <tt>[guest1] $ sudo vgcreate -M 2 -s 1m -c y GuestVolGroup /dev/etherd/e0.1</tt> * edit <tt>/etc/lvm/lvm.conf</tt> and make sure to set locking_type to DLM * before further stuff can proceed, the cluster needs to be up and <tt>clvmd</tt> needs to be running everywhere. So, in VMware I cloned <tt>guest1</tt> twice: as <tt>guest2</tt> and <tt>guest3</tt>. * edit <tt>/etc/cluster.conf</tt> and name the cluster <tt>'''GuestCluster'''</tt> and set up the three nodes with manual (read: ignored) fencing. * bring up the cluster: ** <tt>$ pdsh -w guest[1-3] sudo service cman start && pdsh -w guest[1-3] sudo service clvmd start</tt> * create the logical volume '''GuestVolume''' and assign the full volume group to it: ** <tt>[guest1] $ sudo lvcreate -n GuestVolume -l 100%VG</tt> * .. and make a GFS2 fs therein: ** <tt>[guest1] $ sudo gfs2_mkfs -j 3 -p lock_dlm -t GuestCluster:GuestFS /dev/GuestVolGroup/GuestVolume</tt> * restart the daemons, then mount and your VMware GFS2 cluster should be good to go! <tt>:)</tt> ==Adding disk space to an LVM'ed VMware guest== Having blithely thought that 4GB of disk space per guest (which Fedora LVMs as <tt>VolGroup00</tt>) would be sufficient, I then <tt>git-clone</tt>d my repo and then didn't have enough space to build my kernels; gak. (Since I'm building things on just one guest and then cloning it, I'm hoping that maybe I can somehow shrink the cloned guests' disks back down to just 4GB.) * in VMware, I went to Edit Virtual Machine Settings -> Add (device). I created a (virtual) SCSI disk, 3GB, allocate on-demand, and added it to my guest. ** after starting the guest, the disk appeared as <tt>/dev/sdb</tt> * create a single partition using the entire device: ** <tt>[guest1] $ fdisk # etc etc '''NB:''' make sure that the partition type is '''0x8e''' (Linux LVM) </tt> * make a single LVM physical volume on it: ** <tt>[guest1] $ pvcreate -M 2 /dev/sdb1</tt> * extend the existing volume group by adding the prepped physical volume: ** <tt>[guest1] $ vgextend VolGroup00 /dev/sdb1</tt> * extend the logical volume to use the entire (now-larger) volume group: ** <tt>[guest1] $ lvextend -l +100%FREE /dev/VolGroup00/LogVOl00</tt> * Inspect things with <tt>pvs</tt>, <tt>vgs</tt>, and <tt>lvs</tt> * extend the filesystem itself within the logical volume (it can handle online resizing): ** <tt>[guest1] $ resize2fs /dev/VolumeGroup00/LogVol00</tt> At this point, hopefully <tt>df -k</tt> should show you a larger volume :)

Return to GFS2 Cluster in VMware.