Our website uses cookies. To find out more information on the cookies we use, please head to our privacy policy.OK

How To Extend the External Filestore Disk in the PxM Platform

This article takes you through the steps of extending your external filestore in Osirium when you start to run out of space.


  • ll snapshots of the Osirium Virtual Appliance have been removed.
  • The user account osirium_support has been enabled and a password set.
  • A current backup of the Osirium server and the External filestore has been taken.

Extending the External Filestore Disk

  • Firstly, within the VMware Management Console, expand the external filestore disk being used by Osirium server.
  • Using the Osirium server Console window, logon using the osirium_support account.
  • Rescan the Osirium server to pick up the changes:
  • At the command line prompt type:

  sudo sh -c "echo 1 > /sys/class/scsi_device/2\:0\:1\:0/device/rescan"

  • The expansion to the external filestore disk should now be seen:

  sudo fdisk -l

  • The Following should display

  osirium_support@osirium-111:~$ sudo fdisk -1
  Disk /dev/sdb: 7516 MB, 7516192678 bytes
  255 heads, 63 sectors/track, 913 cylinders, total 14680064 sectors
  Units = sectors of 1 * 512 = 512 bytes
  Sectore size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimal/optimal): 512 bytes / 512 bytes
  Disk identifier: 0x00000000

  • Resize the physical volume in LVM:

  sudo pvresize --verbose /dev/sdb

  • The Following should display

  osirium_support@osirium-111:~$ sudo pvresize --verbose /dev/sdb
  [sudo] password for osirium_support:
     Using physical columne(s) on command line
     Archiving volumen group "external" metadata (seqno 4).
     Resizing colume "/dev/sdb" to 14678016 sectors.
     Resizing physical volume /dev/sdb from 0 to 2047 extents.
     Updating physical volume "/dev/sdb"
     Creating volume group backup "etc/lvm/backup/external" (seqno 5).
    Physical volume "/dev/sdb" changed
    1 physical(s) resized / 0 physical colume(s) not resized

  • Check that the physical volume has got free space now:

  sudo pvdisplay /dev/sdb

  • The Following should display

  osirium_support@osirium-111:~$ sudo pvdisplay /dev/sdb
    --- Physical volume ---
    PV Name         /dev/sdb
    VG Name         external
    PV Size         8.00 GiB / not usable 3.00 MiB
    Allocatable     yes
    PE Size         4.00 GiB
    Total PE        2047
    Free PE         256
    Allocated PE    1791
    PV UUID         vBgXq-k28w-0TIN-iJPe-7Tpn-GiPc-n1Abui

  • Extend the logical volume to fill it:

  sudo lvextend -l +100%FREE -r /dev/external/external

  • The Following should display

  osirium_support@osirium-111:~$ sudo lvextend -1 +100%Free -R /dev/external/external
  [sudo] password for osirium_support:
  lvextend: invalid option -- 'R'
    Error during parsing of command line.
  osirium_support@osirium-111:~$ sudo lvextend -1 +100%Free -r
    Extending logical volume external to 8.00 GiB
    Logical volume external successfully resized
  resize2fs 1.49.9 (4-Feb-2014)
  Filesystem at /dev/mapper/external-external is mounted on /data/osirium/external; on-line resiszing required
  old-desc-blocks = 1, new-desc-blocks = 1
  The filesystem on /dev/mapper/external-external is now 2096128 blocks long.

  • Check that the logical volume has been extended:

  df -h

  • The Following should display

osirium_support@osirium-111:~$ sudo lvextend -1 +100%Free -R /dev/external/external


Filesystem Size Used Avail Use% Mounted on
tmpfs 809M 572K 809M 1% /run
/dev/mapper/osirium--vg-root 32G 14K 17G 46% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 4.0G 4.0K 4.0G 1% /dev
udev 4.0G 112K 4.0G 1% /run/shm
none 100M 0 100M 0% /run/user
/dev/sda1 236M 95M 130M 43% /boot
/dev/mapper/external-external 7.8G 167M 7.2G 3% /data/osirium/external