Welcome Guest [Log In] [Register]



Posted Image

Welcome to TheWebMachine Networks AWS Support Forum. We hope you enjoy your visit.

You're currently viewing our forum as a guest. This means you are limited to certain areas of the board and there are some features you can't use. If you register, you'll be able to access member-only sections, and use many member-only features such as customizing your profile, sending personal messages, and voting in polls. Registration is simple, fast, and completely free. By registering on the forum, you will also receive exclusive emails regarding new updates and promotions (the terms of which are covered by our unique Total Privacy Policy). You must be registered in order to submit Customer Support Requests!


Register now!


If you're already a member please log in to your account to access all of our features:

Username:   Password:
Add Reply
AWS FreePBX Volumes; AWS volumes
Topic Started: Oct 23 2017, 07:20 AM (61 Views)
vlarsen

Can you give a breif description of the 3 volumes running in AWS FreePBX and what each are for?
/dev/sda1
/dev/sdb
/dev/sdf
Edited by vlarsen, Oct 23 2017, 07:33 AM.
Offline Profile Quote Post Goto Top
 
TheWebMachine
Member Avatar
Administrator
There are only 2 physical volumes attached to an AWS FreePBX instance at launch. They are as follows, as seen on the EC2 Console:
  • /dev/sda1 - This contains all of the software and system files (/), /boot, and swap for the instance.
  • /dev/sdb - This is the /var/spool volume where user data such as call recordings, voicemail, and faxes are stored. You can increase the size of this volume at any time from the EC2 console in order to increase this user data storage to suit your needs.


From an SSH console, you can run the following command to show you all volumes, partitions, and their mount points within the OS:
SSH
 
lsblk


You should see output similar to the following:
SSH
 
...]# lsblk
NAME · MAJ:MIN · RM · SIZE · RO · TYPE · MOUNTPOINT
xvda ····· 202:0 ····· 0 ···· 50G ··· 0 ··· disk
├─xvda1 202:1 ····· 0 ·· 300M ··· 0 ··· part ·· /boot
├─xvda2 202:2 ····· 0 ·· 47.8G ·· 0 ··· part ·· /
└─xvda3 202:3 ····· 0 ··· 1.9G ··· 0 ··· part ·· [SWAP]
xvdb ····· 202:16 ··· 0 ···· 50G ··· 0 ··· disk ·· /var/spool


Things to note:
  • In modern linux OSes, sd[a-p] is seen as xvd[a-p]. /dev/sdb on the EC2 console is /dev/xvdb in linux, etc
  • On EC2 console you will see the first volume attachment as /dev/sda1 instead of /dev/sda. This tells the VM Host which partition within the volume contains /boot. This is an intentional design of AWS. The first volume attached to an instance should always follow this convention or it will not boot
  • xvdb is a full volume partition used for /var/spool. This allows for dynamic resizing of the volume from the EC2 Console. If you power off your instance and then enlarge the volume on the EC2 Console, it will automatically resize the partition when you power on the instance
  • The partitions on xvda cannot be resized in the same manner. However, with over 80% of the / (root) volume free at launch and /var/spool (user data) on its own volume, there should be no space constraints encountered with loading whatever custom software you need as long as your application is storing potentially large user data stores in /var/spool/


If you are seeing an extra volume attached to your instance in the EC2 console, perhaps this is leftover from a volume migration you previously performed? Using lsblk you can see which volume is actually housing your /var/spool mount, either sdb or sdf, and detach the volume that isn't being used.

I hope this helps. Please let us know if you have any additional questions. You can also submit a support ticket or contact us on live chat if you need assistance with your instance(s) by clicking the blue button on the right edge of this forum.





Thank you for choosing AWS FreePBX!

If you like our product, please help us let others know by leaving a review on the AWS Marketplace!

We now have ANNUAL subscriptions available! An Annual Subscription gives you ONE MONTH FREE versus paying hourly.
Visit your AWS Subscriptions page to purchase annual subscription(s) for your instance(s) and start saving today!

Offline Profile Quote Post Goto Top
 
vlarsen


NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 50G 0 disk
├─xvda1 202:1 0 300M 0 part /boot
├─xvda2 202:2 0 47.8G 0 part /
└─xvda3 202:3 0 1.9G 0 part [SWAP]
xvdf 202:80 0 100G 0 disk /var/spool
xvdb 202:16 0 50G 0 disk
Edited by vlarsen, Oct 30 2017, 08:00 AM.
Offline Profile Quote Post Goto Top
 
TheWebMachine
Member Avatar
Administrator
I'm this case, it would appear you migrated spool from xvdb to xvdf but did not disconnect xvdb afterwards. Simply detach this volume xvdb (50G) from the instance from the EC2 console.




Thank you for choosing AWS FreePBX!

If you like our product, please help us let others know by leaving a review on the AWS Marketplace!

We now have ANNUAL subscriptions available! An Annual Subscription gives you ONE MONTH FREE versus paying hourly.
Visit your AWS Subscriptions page to purchase annual subscription(s) for your instance(s) and start saving today!

Offline Profile Quote Post Goto Top
 
« Previous Topic · AWS FreePBX · Next Topic »
Add Reply

FreePBX® is a Registered Trademark of Sangoma Technologies and is used with permission.
TheWebMachine Networks is a fully certified Sangoma partner.