Vultr, Block Storage CentOS

travisdh1

@fuznutz04 How much recording to you expect to be doing in the next 2 weeks? 20G is a LOT of call recordings. I'd keep an eye on it, and add block storage if you need it. Like I said, shouldn't take more than 5 minutes.

Do you know what the file system is? I think the default for CentOS is xfs, but I'd rather be sure. cat /etc/fstab

AdamF

@travisdh1 said in Vultr, Block Storage CentOS:

cat /etc/fstab

[root@xxx ~]# cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Mon May  8 18:05:59 2017
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
/dev/mapper/vg_data-lv_root /                       ext4    defaults        1 1
UUID=2d9dfe5e-db4c-4936-b234-3dbdf62a90e1 /boot                   ext4    defaults        1 2
/dev/mapper/vg_data-lv_swap 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

AdamF

@travisdh1 This system has high usage. I fully expect it to fill up rapidly.

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 This system has high usage. I fully expect it to fill up rapidly.

Ah, ok. Yeah, block is probably your most efficient use of resources for this then.

vgcreate /dev/sdb #I'm assuming the new block storage will show up as an sd device
vgextend /dev/sdb vg_data
lvextend lv_root -l +95%FREE
resize2fs /dev/vg_data/lv_root

Shouldn't take much time at all. As always, we'd want to have a backup available before touching storage things.

AdamF

@travisdh1 said in Vultr, Block Storage CentOS:

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 This system has high usage. I fully expect it to fill up rapidly.

Ah, ok. Yeah, block is probably your most efficient use of resources for this then.
vgcreate /dev/sdb #I'm assuming the new block storage will show up as an sd device
vgextend /dev/sdb vg_data
lvextend lv_root -l +95%FREE
resize2fs /dev/vg_data/lv_root
Shouldn't take much time at all. As always, we'd want to have a backup available before touching storage things.

I'm going to give this a test on a test system just because I have never dealt with Vultr block storage. Then if all is well, I'll give this a go.

I'm assuming if there is an issue with block storage (like there was earlier this week with the NJ data center) that it would cause the VPS to crash. Hopefully this isn't the case.

AdamF

@travisdh1 Thank you for this BTW. I'll probably do this this weekend, but wanted to get prepared and wrap my head around this first.

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Thank you for this BTW. I'll probably do this this weekend, but wanted to get prepared and wrap my head around this first.

Glad to help. LVM is one of my big knowledge wheelhouses if you can't tell.

AdamF

@travisdh1 said in Vultr, Block Storage CentOS:

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Thank you for this BTW. I'll probably do this this weekend, but wanted to get prepared and wrap my head around this first.

Glad to help. LVM is one of my big knowledge wheelhouses if you can't tell.

I noticed. Before I met you this year, I watched your LVM presentation from Mangocon 2016.

stacksofplates

@travisdh1 said in Vultr, Block Storage CentOS:

Because you're using LVM, options 2 and 3 are both doable. To me 2 is quicker and easier, but I've used LVM long enough that I know how to do most of that off the top of my head. The only thing I normally have to lookup is how to expand the file system, because the process tends to be a little different depending on the file system. Real quick here.
pvcreate /dev/device
vgextend volume_group_name /dev/device
lvextend logical_volume_name -l +95%FREE
xfs_growfs /dev/volume_group_name/logical_volume_name
done. Shouldn't take but 5 minutes, if that.

Edit: I normally go with either 90% or 95% of the available space in the volume group to keep space available for a local snapshot.

If you pass -r to lvextend it will auto resize the filesystem. That way you don't need to remember the differences between them.

AdamF

@stacksofplates said in Vultr, Block Storage CentOS:

@travisdh1 said in Vultr, Block Storage CentOS:
Because you're using LVM, options 2 and 3 are both doable. To me 2 is quicker and easier, but I've used LVM long enough that I know how to do most of that off the top of my head. The only thing I normally have to lookup is how to expand the file system, because the process tends to be a little different depending on the file system. Real quick here.
pvcreate /dev/device
vgextend volume_group_name /dev/device
lvextend logical_volume_name -l +95%FREE
xfs_growfs /dev/volume_group_name/logical_volume_name
done. Shouldn't take but 5 minutes, if that.

Edit: I normally go with either 90% or 95% of the available space in the volume group to keep space available for a local snapshot.
If you pass -r to lvextend it will auto resize the filesystem. That way you don't need to remember the differences between them.

So you are saying instead of this:

 lvextend logical_volume_name -l +95%FREE

Use this:?

lvextend logical_volume_name -r

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@stacksofplates said in Vultr, Block Storage CentOS:
@travisdh1 said in Vultr, Block Storage CentOS:
Because you're using LVM, options 2 and 3 are both doable. To me 2 is quicker and easier, but I've used LVM long enough that I know how to do most of that off the top of my head. The only thing I normally have to lookup is how to expand the file system, because the process tends to be a little different depending on the file system. Real quick here.
pvcreate /dev/device
vgextend volume_group_name /dev/device
lvextend logical_volume_name -l +95%FREE
xfs_growfs /dev/volume_group_name/logical_volume_name
done. Shouldn't take but 5 minutes, if that.

Edit: I normally go with either 90% or 95% of the available space in the volume group to keep space available for a local snapshot.
If you pass -r to lvextend it will auto resize the filesystem. That way you don't need to remember the differences between them.
So you are saying instead of this:
 lvextend logical_volume_name -l +95%FREE
Use this:?
lvextend logical_volume_name -r

More like

lvextend logical_volume_name -l +95%FREE -r

AdamF

@travisdh1 Thanks

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Thanks

If you want to just look at how powerful LVM has become through the years, you should run lvm and look at the help screens sometime. That's how I dived into it initially at least.

AdamF

@travisdh1 Run LVM? You mean just look at the man pages? Or are you referring to something else?

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Run LVM? You mean just look at the man pages? Or are you referring to something else?

It's got a whole environment just for its self. Literally just lvm on a command line.

AdamF

@travisdh1 Ah nice. Will do. I want to learn a lot more about it, so I'll take your advice.

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Ah nice. Will do. I want to learn a lot more about it, so I'll take your advice.

The amount of options is almost staggering. Even more, ZFS, brtfs and a number of other filesystems have just as many options and choices to make.

AdamF

@travisdh1 said in Vultr, Block Storage CentOS:

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Ah nice. Will do. I want to learn a lot more about it, so I'll take your advice.

The amount of options is almost staggering. Even more, ZFS, brtfs and a number of other filesystems have just as many options and choices to make.

Yeah, one at a time. I've worked with ZFS in the past, but it was when I was using FreeNAS back in the day.

travisdh1

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 said in Vultr, Block Storage CentOS:

@fuznutz04 said in Vultr, Block Storage CentOS:

@travisdh1 Ah nice. Will do. I want to learn a lot more about it, so I'll take your advice.

The amount of options is almost staggering. Even more, ZFS, brtfs and a number of other filesystems have just as many options and choices to make.

Yeah, one at a time. I've worked with ZFS in the past, but it was when I was using FreeNAS back in the day.

At least it's all the same stuff, just called something different for the most part.

AdamF

@travisdh1 Right. Seeing as how the world is built on storage systems, I need to dig in a little.

That's all for now. Good night NotJengaMaster.