support.scalearc.com Open in urlscan Pro
34.226.9.20  Public Scan

Form analysis
1 forms found in the DOM

/search

<form action="/search" id="omnisearch" autocomplete="off">
  <div class="input-wrap">
    <i class="fa fa-search"></i>
    <a href="#" class="search-clear" style="display: none;"><i class="fa fa-times"></i></a>
    <input type="text" class="omnisearch" name="q" autocomplete="off" placeholder="Search...">
    <!-- .active on this if we need it active -->
  </div>
  <button type="submit" class="search-btn">Search</button>
  <div class="dp-react-widget"><!-- react-empty: 1 --></div>
</form>

Text Content

Navigate

 * 
 * 
 * Login to Ignite Global Support


Search

or
Contact Us


 * GET IN TOUCH
   
   Send us an email


 * SUBMIT FEEDBACK
   
   Feedback and suggestions submitted by customers like you

 * Knowledgebase Read help articles
 * Feedback Custom suggestions
 * Downloads Browse our downloads
 * Contact Us We are here to help

 * Portal
 * Knowledgebase
 * Databases
 * Mounting new partition in ScaleArc

Subscribe Download PDF


MOUNTING NEW PARTITION IN SCALEARC

Sanjay More

--------------------------------------------------------------------------------

2016-07-26

--------------------------------------------------------------------------------

0 Comments

--------------------------------------------------------------------------------

in Databases


MOUNTING NEW DATA PARTITION IN SCALEARC

Release Classification Level DB Platform Categories All How To


ISSUE DESCRIPTION

If the disk provided on ScaleArc is found insufficient to hold various logs and
analytics data generated by ScaleArc, It's Disk Management Service ensures the
space required to continue ScaleArc operation by deleting the old logs and old
analytics data.

In this case, you may like to provide more space to manage more logs and
analytics data.

 

Follow the instructions below to add new partition and mount volume to ScaleArc.

You need to login to ScaleArc's backend using SSH client like putty.

Make sure you have enable SSH login on ScaleArc.

You will need root privileges to add new partiton. Hence switch user to root.

 

# sudo su -

 

Finding the New Hard Drive in CentOS 6

# ls /dev/sd*

/dev/sda  /dev/sda1  /dev/sda2 /dev/sdb

Creating Linux Partitions

 

The next step is to create one or more Linux partitions on the new disk drive.
This is achieved using the fdisk utility which takes as a command-line argument
the device to be partitioned:

# su -

# fdisk /dev/sdb

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF
disklabel

Building a new DOS disklabel with disk identifier 0xd1082b01.

Changes will remain in memory only, until you decide to write them.

After that, of course, the previous content won't be recoverable.

 

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)

 

WARNING: DOS-compatible mode is deprecated. It's strongly recommended to

         switch off the mode (command 'c') and change display units to

         sectors (command 'u').

 

Command (m for help):

In order to view the current partitions on the disk enter the p command:

Command (m for help): p

 

Disk /dev/sdb: 334.4 GB, 343597383698 bytes

255 heads, 63 sectors/track, 4177 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0xd1082b01

 

   Device Boot      Start         End      Blocks   Id  System

Command (m for help): n

Command action

   e   extended

   p   primary partition (1-4)

p

Partition number (1-4):

In this example we only plan to create one partition which will be partition 1.
Next we need to specify where the partition will begin and end. Since this is
the first partition we need it to start at the first available sector and since
we want to use the entire disk we specify the last sector as the end. Note that
if you wish to create multiple partitions you can specify the size of each
partition by sectors, bytes, kilobytes or megabytes.

 

Partition number (1-4): 1

First sector (2048-67108863, default 2048):

Using default value 2048

Last sector, +sectors or +size{K,M,G} (2048-67108863, default 67108863):

Using default value 67108863

Now that we have specified the partition we need to write it to the disk using
the w command:

Command (m for help): w

The partition table has been altered!

 

Calling ioctl() to re-read partition table.

Syncing disks.

If we now look at the devices again we will see that the new partition is
visible as /dev/sdb1:

# ls /dev/sd*

/dev/sda /dev/sda1 /dev/sda2 /dev/sdb /dev/sdb1

 

 The next step is to create a file system on our new partition.

Creating a File System on a CentOS 6 Disk Partition

# /sbin/mkfs.ext4  /dev/sdb1

mke2fs 1.41.12 (17-May-2010)

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

Stride=0 blocks, Stripe width=0 blocks

2097152 inodes, 8388352 blocks

419417 blocks (5.00%) reserved for the super user

First data block=0

Maximum filesystem blocks=4294967296

256 block groups

32768 blocks per group, 32768 fragments per group

8192 inodes per group

Superblock backups stored on blocks:

        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

        4096000, 7962624

 

Writing inode tables: done

Creating journal (32768 blocks): done

Writing superblocks and filesystem accounting information: done

 

This filesystem will be automatically checked every 36 mounts or

180 days, whichever comes first.  Use tune2fs -c or -i to override.

Mounting a File System

Now that we have created a new file system on the Linux partition of our new
disk drive we need to mount it so that it is accessible. In order to do this we
need to create a mount point. A mount point is simply a directory or folder into
which the file system will be mounted. For the purposes of this example we will
create a /backup directory to match our file system label (although it is not
necessary that these values match):

# mkdir /tempdata

The file system may then be manually mounted using the mount command:

# mount /dev/sdb1 /tempdata

 

 

STOP ScaleArc Service, Analytics Service from ScaleArc User Interface.

# /etc/init.d/idblb stop

# /etc/init.d/idb_watchdog stop

# /etc/init.d/analytics stop

Copy all logs data into /tempdata folder

Copy all data from /data folder i.e. /data/logs and /data/cache folder to newly
created /tempdata folder.

# cp –Rfp /data/* /tempdata/

 

Rename the existing /data folder to /data.old

# mv /data /data.old

 

Unmount the new volume (/tempdata)

# cd /

# umount /tempdata

 

Mount the new partition to /data

# mount /dev/sdb1 /data

 

Configuring CentOS 6 to Automatically Mount a File System

In order to set up the system so that the new file system is automatically
mounted at boot time an entry needs to be added to the /etc/fstab file.

The following example shows an fstab file configured to automount our /backup
partition:

…..

…..

 

tmpfs          /dev/shm            tmpfs   defaults        0 0

devpts         /dev/pts            devpts  gid=5,mode=620  0 0

sysfs          /sys                sysfs   defaults        0 0

proc           /proc               proc    defaults        0 0

/dev/sdb1      /data        ext4    defaults       0 0

 

 Reboot ScaleArc box.

Now check if things are getting logged correctly.

You are done !

In case you need any assistance, feel free to contact ScaleArc Support.

 

rc |  Feedback

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

Permalink: https://support.scalearc.com/kb/articles/3600


RATE THE QUALITY OF THIS PAGE

This page was helpful :) :( This page was not helpful

--------------------------------------------------------------------------------

Quick Jump
 * ScaleArc Customer Support
 * Knowledgebase
 * Downloads
 * Feedback
 * Contact Us

Top
Helpdesk software provided by DeskPRO