Skip to main content

Grow LUN and add partition to VMware Virtual DIsk for Red Hat

Red Hat 5.6 running on VMware vSphere.

Grab a snapshot before messing with any of this.
This procedure is slightly different if you are messing with /dev/sda (if that's where your / is)


# Determine what VGs are assigned to the disk you are messing with...
#   in this case... /dev/sdb
for PART in `fdisk -l /dev/sdb | grep ^/dev | awk '{ print $1 }'`; do pvdisplay $PART | grep VG\ Name | awk '{ print $3 }' | sort -u; done
vg_test

# Figure out what volumes are mounted on that VG
df -h | grep SCOREDATA

umount /SCORE_Data
lvchange -a n /dev/SCOREDATA/SCORE_Data
vgchange -a n SCOREDATA
blockdev --rereadpt /dev/sdb
fdisk -u /dev/sdb
# n p 2 t 8e w
partprobe /dev/sdb
blockdev --rereadpt /dev/sdb
fdisk -l /dev/sdb
vgchange -a y SCOREDATA
mount -a
pvcreate /dev/sdb2
vgcreate SCOREARCH /dev/sdb2
FREEPE=`pvdisplay /dev/sdb2 | grep Free\ PE | awk '{ print $3 }'`
echo $FREEPE
lvcreate -l+${FREEPE} -nSCORE_Archive SCOREARCH
mkfs /dev/SCOREARCH/SCORE_Archive
cp /etc/fstab /etc/fstab.20130319.jr
echo "/dev/SCOREARCH/SCORE_Archive /SCORE_Archive ext4 defaults 1 2" >> /etc/fstab
mount -a
chown jboss:jboss /SCORE_Archive/

[root@myserver01 /]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol01
                       14G  9.0G  3.9G  70% /
/dev/sda1             2.0G   49M  1.8G   3% /boot
tmpfs                 2.0G     0  2.0G   0% /dev/shm
/dev/mapper/SCOREDATA-SCORE_Data
                       99G   46G   48G  49% /SCORE_Data
/dev/mapper/SCOREARCH-SCORE_Archive
                      247G   60M  234G   1% /SCORE_Archive
[root@myserver01 /]# vgs
  VG         #PV #LV #SN Attr   VSize   VFree
  SCOREARCH    1   1   0 wz--n- 250.00G    0
  SCOREDATA    1   1   0 wz--n- 100.00G 4.00M
  VolGroup00   1   2   0 wz--n-  17.97G    0
[root@myserver01 /]# lvs
  LV            VG         Attr   LSize   Origin Snap%  Move Log Copy%  Convert
  SCORE_Archive SCOREARCH  -wi-ao 250.00G                                    
  SCORE_Data    SCOREDATA  -wi-ao  99.99G                                    
  LogVol00      VolGroup00 -wi-ao   4.00G                                    
  LogVol01      VolGroup00 -wi-ao  13.97G

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.