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.
-
@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.
-
@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.
-
@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.
-
@fuznutz04 said in Vultr, Block Storage CentOS:
@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.
whispers it's the glasses
-
@travisdh1 So on second thought, I'm thinking it might be a better approach to redirect the call recordings to the block device directly, without extending the LVM volume to the block device. So it would be like this:
Attach block device and create partition and file system.
Mount the new device to a new directory (/callrecordings)
In FreePBX, point the call recordings to this new directory.This way, the VPS disk, is still completely separate from the block device disk. In my head, this just seems cleaner, and has less potential for errors if the block device is ever unavailable.
Thoughts?
-
@fuznutz04 said in Vultr, Block Storage CentOS:
@travisdh1 So on second thought, I'm thinking it might be a better approach to redirect the call recordings to the block device directly, without extending the LVM volume to the block device. So it would be like this:
Attach block device and create partition and file system.
Mount the new device to a new directory (/callrecordings)
In FreePBX, point the call recordings to this new directory.This way, the VPS disk, is still completely separate from the block device disk. In my head, this just seems cleaner, and has less potential for errors if the block device is ever unavailable.
Thoughts?
Yes, that makes way more sense.
-
@scottalanmiller said in Vultr, Block Storage CentOS:
@fuznutz04 said in Vultr, Block Storage CentOS:
@travisdh1 So on second thought, I'm thinking it might be a better approach to redirect the call recordings to the block device directly, without extending the LVM volume to the block device. So it would be like this:
Attach block device and create partition and file system.
Mount the new device to a new directory (/callrecordings)
In FreePBX, point the call recordings to this new directory.This way, the VPS disk, is still completely separate from the block device disk. In my head, this just seems cleaner, and has less potential for errors if the block device is ever unavailable.
Thoughts?
Yes, that makes way more sense.
The only thing that made me think of that was because about 2 weeks ago Vultr NJ had some issues with block storage. If they have an issue again, at least I could still boot the VM. (although I would have to remove the block device from the fstab. But then, It should boot fine I suppose. (crosses fingers)
