You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Use at your own risk


Please Note:

This is a Suggestion on how to increase Disk Space in your eDMS OVA with the Help of LVM (Logical Volume Manager)

The following instruction are common and basic Linux System and LVM Administration and not proprietary to the eDMS nor its developers.

Always ensure a proper backup is in place prior to any such administrative work is started.

Client takes on full responsibility for the execution of this task. This should not be attempted unless you are qualified.

This being said, there are a number of huge advantages to extend your Diskspace via LVM over other means (e.G. you do not have to split up your storage voer several logical mountpoints) and this has proven to be reliable, scalable and fast.

Should you have the need for increasing your Diskspace and are not feeling comfortable with this procedure, please feel free to contact Patrix, Serviva or Pace-Ip for assistance.

Add Harddisk Space in your Hypervisor Environment

Regardless of your Usage of VMWare, Xen, Hyper V or other, when you intend to grow the Diskspace of the eDMS OVA, it is neccesary to assign Diskspace to your VM

Please refer to the Manual of your Virtualization Platform for this.

The Standard Size while deploying the OVA is 100 GB. This will naturally not suffice anymore after a while of adding Documents, Versions Previews etc.

We cannot give a general Recommendation as to how large your extension should become, but please contact us if this is unclear in your specific Situation.


Make Disk visible to the OVA


  • SSH into the CentOS OVA and sudo to root (unless you are already root)

    sudo su -

List the block device to see the newly assigned vSphere hard disk.

lsblk

If you do not see the vSphere hard disk, force a rescan (or reboot which is less elegant but just as effective)

for host in $(ls -1d /sys/class/scsi_host/*); do echo "- - -" > ${host}/scan ; done
for device in $(ls -1d /sys/class/scsi_disk/*); do echo "1" > ${device}/device/rescan ; done

create a new Partition that is compatible to LVM


  • Format the disk partition. Get the device name from the previous lsblk output

    fdisk /dev/sdb
n (new partition)
p (primary)
(Press ENTER) (Use default partition number)
(Press ENTER) (Use default first sector)
(Press ENTER) (Use default last sector)

t (change the partition type)
8e (Linux LVM)

w (write)

    in order to see this partition, read the partition table with "partprobe" (or reboot which is less elegant but just as effective)

Create the Physical Volume for LVM

and check afterwards with pvs

Extend the Volumegroup (vg).

first check for the group with "vgs" then "vgextend centos" then check again:


now extend the Logival Volume (lv)

first check for the Volume with "vgs" then "lvextend" then check again:

resize filesystem

now in order to actually use the additional space we need to resize the filesystem.
first check the existing file system

then actually resize  the file system

and check again:

Voila!


In essence

  1. Increase Diskspace (physically or on the Hypervisor Layer)
  2. Reboot or rescan for disks
  3. create a new Partition that is compatible to LVM
  4. re-read Partition table either via reboot or command "partprobe"
  5. Initialise a new PV with pvcreate
  6. Increase  the VG with vgextend
  7. Increase  the LV with lvextend
  8. Increase the Filesystem with resize2fs




  • No labels