LVM Partition resize
-
I installed a new FrePBX box, and neglected to change the root partition size from the standard 50GB to something bigger. Instead, most of the free space is allocated to /dev/mapper/s7_freepbx-home. See below.
df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/s7_freepbx-root 50G 46G 4.9G 91% / devtmpfs 7.8G 0 7.8G 0% /dev tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 7.8G 33M 7.8G 1% /run tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup /dev/vda1 1014M 129M 886M 13% /boot /dev/mapper/vg_callrecordings-lv_callrecordings 394G 321M 374G 1% /callrecordings /dev/mapper/s7_freepbx-home 142G 409M 141G 1% /home tmpfs 1.6G 0 1.6G 0% /run/user/1000 tmpfs 1.6G 0 1.6G 0% /run/user/995
What is the best procedure to take space from /dev/mapper/s7_freepbx-home and expand the /dev/mapper/s7_freepbx-root directory?
-
@fuznutz04 Reinstall?
-
Not an option at this point.
-
@JaredBusch said in LVM Partition resize:
@fuznutz04 Reinstall?
I hate to say it but I agree. Not because @JaredBusch said it, but because it is the easiest way.
-
I would install cockpit because I can never recall all of the lv/pv commands. I do not resize things often enough.
-
@fuznutz04 said in LVM Partition resize:
Not an option at this point.
The way you wrote it, it seemed like a new install. I take it this is older? Looking at the screenshot closer I see disk filling.
WTF are you filling
/
up with? -
Yeah, I'm trying to figure out what is taking space now.
-
@fuznutz04 said in LVM Partition resize:
Yeah, I'm trying to figure out what is taking space now.
-
here is my post on the freePBX community about it
https://community.freepbx.org/t/innodb-file-ibdata1-growing-too-large/51910 -
@JaredBusch Good grief! That log file is 20 GB!
-
Read the thread on the FreePBX community, it is fucking stupid answers as to why.
-
@JaredBusch !?!?! Normal? oh boy.
-
@fuznutz04 said in LVM Partition resize:
@JaredBusch !?!?! Normal? oh boy.
Only for poorly written dashboards.... Just another little thing that annoys me with FreePBX and pushing me towards VitalPBX.
Not annoying enough to migrate (expensive) a workload though.Once you redo the logging to create individual log files, it is easy enough to dump and recreate that specific table. Which dumps the log file for that table.
-
20 GB? Normal. 20 KB? also normal. :man_facepalming:
-
@JaredBusch said in LVM Partition resize:
@fuznutz04 said in LVM Partition resize:
@JaredBusch !?!?! Normal? oh boy.
Only for poorly written dashboards.... Just another little thing that annoys me with FreePBX and pushing me towards VitalPBX.
Not annoying enough to migrate (expensive) a workload though.Once you redo the logging to create individual log files, it is easy enough to dump and recreate that specific table. Which dumps the log file for that table.
So you just did exactly what was in this post here, right? http://www.pc-freak.net/blog/fix-mysql-ibdata-file-size-ibdata1-file-growing-large-preventing-ibdata1-eating-disk-space/
And I agree. I am actually concerned with what is going to happen with FPBX now that the majority of the "main players" have left.
-
@fuznutz04 yes, I did exactly that.
Then whenever things got full again, I was able to simply drop/create the one table without stopping anything.
-
@JaredBusch said in LVM Partition resize:
@fuznutz04 yes, I did exactly that.
Then whenever things got full again, I was able to simply drop/create the one table without stopping anything.
Well, looks like I know what i'll be doing tonight.