Unsolved
This post is more than 5 years old
1 Rookie
•
63 Posts
1
12828
InsightIQ Local /datastore Expansion
Hello,
Working on a new implementation of InsightIQ. The default /datastore size
created by the OVA is 6.5GB, and we'd like to expand this. How do we expand
the local /datastore file system? We've already expanded the ESX datastore
that supports the InsightIQ VM.
Please note that we do NOT want to use NFS for /datastore. We want to
expand the local /datastore file system.
Thanks in advance,
Will S.
johnsonka
130 Posts
1
September 22nd, 2015 13:00
Hello WillSanders ,
Thank you for your question! To expand the datastore partition on InsightIQ, you will need to create a new virtual disk and move the data (if there is any.) If you have a login to EMC online support, you can follow the resolution in this Knowledge Base article:
https://support.emc.com/kb/167800
If you do not have a login to EMC online support, send me a message and I can get the information you need. Please let me know if there is anything else I can do for you.
WillSanders
1 Rookie
1 Rookie
•
63 Posts
0
September 23rd, 2015 06:00
Katie,
Thanks for the response. I do have access to support.emc.com, but following the link I get an "Access Denied" error.
Can you forward me the information?
Thanks,
Will
dynamox
2 Intern
2 Intern
•
20.4K Posts
5
September 23rd, 2015 07:00
Issue
Statistics from Isilon clusters are no longer being gathered. This issue applies to all virtual machine (VM) installations of InsightIQ.
NOTE
This article applies only to Virtual Machines provided by Isilon. For physical machines, please refer to your system documentation about how to add devices.
Symptoms
The /var/log/insightiq.log file on the InsightIQ VM contains entries similar to the following:
Isilon OneFS
Isilon InsightIQ
The amount of data being gathered for InsightIQ exceeds the allotted datastore size.
NOTE
By default, the InsightIQ datastore is 64 GB in size.
Solution
Perform the following steps to create a new, larger local datastore, configure InsightIQ to use the new datastore, and copy the existing data from the old datastore to the new datastore.
sudo shutdown -P now
sudo -s
fdisk –l
You will probably also see a message similar to the following:
Disk /dev/sdc doesn't contain a valid partition table
NOTE
In these steps, we use the name /dev/sdc as an example for the name of the new drive. The name may vary with your configuration but it will always be in /dev.
echo -e "n\np\n1\n\n\nw" | fdisk
For example:
echo -e "n\np\n1\n\n\nw" | fdisk /dev/sdc
Alternatively, you can create the partition manually as follows:
sudo fdisk
For example:
sudo fdisk /dev/sdc
IMPORTANT!
If any defined partitions are displayed in the partition table, do not continue this procedure. Stop here and contact Isilon Technical Support for additional instructions.
fdisk -l
The new datastore should be listed with a valid partition, similar to the following. Note that the new partition will be listed as /dev/sdc1 if the drive name is /dev/sdc.
Disk /dev/sdc: 107.4 GB, 107374182400 bytes
255 heads, 63 sectors/track, 13054 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: 0x1c51664b
Device Boot Start End Blocks Id System
/dev/sdc1 1 13054 104856223+ 83 Linux
mkfs -t ext3
For example:
mkfs -t ext3 /dev/sdc1
mkdir /datastore_tmp
For InsightIQ 2.5 and later:
iiq_stop
For InsightIQ 2.1 and earlier:
sudo stop insightiqNOTE
Data will not be collected from the monitored clusters while the InsightIQ application is stopped.
sudo service iiq_db stop
mount /datastore_tmp
For example:
mount /dev/sdc1 /datastore_tmp
df -h
Output similar to the following appears:
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 2.3G 1.1G 1.1G 51% /
tmpfs 939M 0 939M 0% /dev/shm
/dev/sda1 243M 26M 205M 12% /boot
/dev/sdb1 63G 545M 60G 1% /datastore
172.16.132.137:/ifs 40G 3.9G 16G 20% /net/172.16.132.137/ifs
172.16.132.137:/ifs/.ifsvar/modules/fsa
40G 3.9G 16G 20% /net/172.16.132.137/ifs/.ifsvar/modules/fsa
/dev/sdc1 99G 188M 94G 1% /datastore_tmp
cp -rp /datastore/. /datastore_tmp/
diff -rq /datastore /datastore_tmp
If the directories are identical, you will be returned to a command prompt. Otherwise, a list of differences will be displayed.
If there are differences, you might need to re-copy the missing files. Contact Isilon Technical Support if you need assistance.
cp -v /etc/fstab /etc/fstab.bak
dumpe2fs /dev/sdc1 | grep UUID
CAUTION!
The system might be rendered inoperable if configuration files are edited incorrectly. Before editing a configuration file, create a backup of the file so that the file can be restored if necessary.
Example /etc/fstab file for InsightIQ 2.5 and later:
UUID=46f94d79-787a-40b4-b406-6e419f1f5d53 / ext3 defaults 1 1
UUID=f2ed68f4-a4d4-4c01-b3c1-cc436b47e3c8 /boo ext3 defaults 1 2
UUID=527ffcb4-d9cf-4eb0-b46c-896e8b98907e swap swap defaults 0 0
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 /datastore ext3 defaults 0 0
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /datastore ext3 defaults 0 0Example /etc/fstab file for InsightIQ 2.1 and earlier:# /etc/fstab: static file system information.
#
proc /proc proc defaults 0 0
/dev/sda1 / ext4 defaults 0 0
/dev/sda2 swap swap defaults 0 0
# /dev/sdb1 /datastore ext3 defaults 0 0
UUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx /datastore ext3 defaults 0 0
Example line before the change:
/dev/sdb1 /datastore ext3 defaults 0 0
Example line after the change:
# /dev/sdb1 /datastore ext3 defaults 0 0
reboot
mount | grep datastore
You should see the new partition mounted
UUID= on /datastore type ext3 (rw)
For example:
UUID=79159458-5e18-42d1-96b0-d2c90458bf6b on /datastore type ext3 (rw)
sudo rmdir /datastore_tmp/
Reverting to the previous datastore
If these changes need to be reverted, you can revert to the old /etc/fstab by running the folliwng command and then rebooting: Alternatively, you can shut down and revert to a snapshot if one was taken.Remove the old datatstore
After confirming that the new datastore works as expected and contains all the desired historical data, you can remove the old datastore:Additional information
Related article:WillSanders
1 Rookie
1 Rookie
•
63 Posts
0
September 23rd, 2015 13:00
Thanks
WillSanders
1 Rookie
1 Rookie
•
63 Posts
0
September 23rd, 2015 13:00
Can we get this information added to the InsightIQ installation guide? At the very least can we get some details added about disk space layout for local directories? Without this KB there is no way to plan how to build the InsightIQ VM structure.
Further, is there a reason that the command "parted" is not in the CentOS release being used for the InsightIQ VM?
Thanks,
Will S.
jason_f1
8 Posts
1
September 23rd, 2015 16:00
I just used this KB article to add more storage to an InsightIQ 3.0.1 instance. It worked perfectly. Thanks!
johnsonka
130 Posts
0
September 24th, 2015 06:00
Hello WillSanders ,
Thank you for your feedback. I will pass the documentation request along to the team.
As for the "parted" command, the OVA was designed to be very stripped down and easily packaged by engineering, and I cannot speak to their decision to remove certain commands over others; however, you can install any command you would like through the "yum" package manager. I use this functionality a lot myself to add commands to my OVAs to customize them to my needs.
Please let me know if you have any additional questions or concerns.
tamartin
3 Posts
0
September 24th, 2015 08:00
Hi everyone,
The best way to submit documentation feedback and content requests is to send an email to isicontent@emc.com.
WillSanders , I forwarded your request to update the IIQ docs to the documentation feedback team.
Thanks!
Travis