Hi kelly_zarate,

(preliminary word of caution: If things go wrong, your system can be wrecked. So before starting below steps, have some form of backup for your system, i. e. a snapshot done by VMware, if that's what it is running on.)

> /dev/mapper/system-root

so you are running LVM? Please check by running the commands "vgs" (showing a list of configured volume groups - it should show a row for "system"), "lvs" (showing all logical volumes, at least one for "root" on "system") and "pvs" listing all known physical volumes, at least /dev/sda2).

I'd be interested in the output of "pvs" - does it list /dev/sda2 and is it already showing the increased size (assuming that you have resized the partition according to the KB article you referenced, and then rebooted the machine)?

If you're on LVM, you could have avoided resizing that existing partition, because that KB article is for those default installs where BtrFS is on a *partition* (which cannot be resized live). With LVM, you could have simply used that added space as a *new* partition, added it to the volume group and then resize your logical volume, like you are to do now anyhow:

Once your PV knows about the size change (as it should do after a reboot - if not, call "pvresize /dev/sda2" explicitly), your volume group will show the new available room as "VFree" in the "vgs" command output. It's then only required to add some (or all) of that space to your root file system's logical volume by calling i. e. "lvresize -L +50G /dev/system/root" (to add 50 GB of space). So now you have a larger "partition" (actually a "logical volume") with BtrFS on it - but that file system (not yet) knows about that added space. So the last step is to resize the file system: "btrfs filesystem resize max /"

Again, only follow these steps if you're actually on LVM (thus "vgs" is showing the VG "system") and after having made sure you have a way to revert the changes if things go wrong (i. e. via a snapshot of your VM).

Regards,
J