Hi @ninjaplys
Welcome to the community. I’d recommend getting familiar with the regular disk commands first.
To see what file systems are mounted and how much they’re being used:
df -hT
To get an overview of all your block devices and logical volumes and where they all reside:
lsblk
When working with Logical Volumes you will see the following terms:
-
PV (Physical Volume): This refers to a physical disk, or a partition on the disk. If you used a tool like fdisk to make 2 partitions on a disk they will show as two PVs. You can list them with the command
pvsor get more info withpvdisplay -
VG (Volume Group): You add your PVs to volume groups and with will be the pool used for the logical volumes in that group. You can list your VGs with
vgsand get more info withvgdisplay -
LV (Logical Volume): This is where the magic happens. An LV can be resized, extended, span multiple disks. Once you create an LV you would next format it with a file system. You can list them with
lvs`` and get more info withlvdisplay```.
To answer your question, I’d recommend extending / to like 20G and then creating a new LV for the rest of your data you plan to store via SAMBA.
- To extend root to 20G. The
-roption tells it to resize the file system too:
lvextend -L20G -r /dev/mapper/fedora_fedora-root
- To create a new VG called “fedora-shares”:
lvcreate -L 190G -n fedora-shares fedora
- Extend it to use the full disk:
lvextend -l+100%FREE /dev/mapper/fedora_fedora-shares
- Format is with a file system:
mkfs.xfs /dev/mapper/fedora_fedora-shares
- Create a mountpoint and add it to your /etc/fstab:
mkdir -p /srv/shares
echo "/dev/mapper/fedora_fedora-shares /srv/shares xfs defaults 0 0" >> /etc/fstab
- Test it by mounting it:
mount -a
- Finally, use
dfandlsblkto verify the new LV is mounted and ready to use