ScaleArc Support Center

Welcome back, guest

Register or login below.

Feedback

How It Works: Why Does a ScaleArc instance spun up from AWS Marketplace Default to 100 GB Disk?

 

How It Works: Why Does a ScaleArc instance spun up from AWS Marketplace Default to 100 GB Disk?

 
Release Classification Level DB Platform Categories
Uptill 3.10 Procedure

 

ALL Configuration
  
QUESTION

  1. Why does any ScaleArc Instance spun up in AWS marketplace [ex: M4.xlarge, C4.xlarge] result in allocating 100GB for '/data' 
  2. How can it be increased?

ANSWER

  1. Why does any ScaleArc Instance spun up in AWS marketplace [ex: M4.xlarge, C4.xlarge] result in allocating 100GB for '/data' ?

    ScaleArc images built of OVA that are available in various instances default to reserved 100 GB for '/data'. If you choose to add a second volume of higher size as shown below, it would still allocate only 100 GB to the Volume Group that has '/data' mounted on it.

  2. How can it be increased?
SSH access into the ScaleArc console is required to perform steps to extend and resize Logical Volume. Below are the steps involved -
  • Understanding current disk layout

df -kh [To see which disk /data is mounted on]

fdisk -l [To check all available disks and partitions]

pvdisplay  [to get PV Name & VG Name]
Example -

 -- PV Name  /dev/xvdf1

 -- VG Name vg_data

lvdisplay [to get LV Path , LV Name , VG Name & LV Size]

Example -

 -- LV Path /dev/vg_data/lv_data

 -- LV Name lv_data

 -- VG Name vg_data

 -- LV Size 99 GiB

For instance from above 4 commands we can learn that '/dev/xvdf1' has 'vg_data' and 'lv_data' 

  • Below are steps to expand LV

fdisk -l

Disk /dev/xvdf: 1073 GB

 /dev/xvdf1 

fdisk -l /dev/xvdf

   n (new)

   p (partition) 

   2 (2nd as 1st partition already exist)

   default enter/return key (starts where 1st partition ends)

   default enter/return key (ends at last cylinder)

   t (change partitions system ID)

   2 (give which partition #)

note: 83 = Linux   8e = Linux LVM

   8e

   w

note: warnings are about reboot to commit the changes

   fdisk -l (to confirm 2nd partition)

   reboot

  •  After system comes back up perform below to check size of newly created partition

fdisk /dev/xvdf2 (The new partition just created)

 p

  •  Steps to perform the extend

vgextend vg_data /dev/xvdf2

              (VG Name) (new partition)

     physical volume "/dev/xvdf2" successfully created

     Volume group "vg_data" successfully extended

lvextend -l +100%free /dev/vg_data/lv_data

                                                 (LV Path)

resize2fs /dev/vg_data/lv_data

                          (LV Path)

df -kh (to confirm extended disk)

Above steps should expand the disk for '/data' online.

 

 

Copyright ©2014 ScaleArc, Inc. All rights reserved. Contact Support |  Contact ScaleArc |  Feedback

2901 Tasman Drive Santa Clara, CA 95054 | Email:  support@scalearc.com

 

 

Permalink: https://support.scalearc.com/kb/articles/3957
Subscribe to this article to get an email notification when it is updated.
Share this: