Robert McBroom via users wrote:
> Installed the server version of Fedora in a lvm physical
> volume.
[...]
> Quickly started running out of space. Created a second
> physical volume and used vgextend to add it to the volume
> group.
>
> ~]# vgextend fedora_hpz440 /dev/nvme0n1p6
>
> Increased the size of the logical volume with some of the
> space of the second physical volume.
>
> ~]# lvextend -L +150G /dev/mapper/fedora_hpz440/root
Adding --resizefs to the lvextend command would do the
trick. That calls fsadm to do the resizing, so you could
just run fsadm now to finish resizing the underlying
filesystem. Something like:
fsadm resize /dev/mapper/fedora_hpz440/root
Though it's worth reading fsadm(8) to check the options. It
has a check command as well as --dry-run (-n) for use with
the resize command.
The fsadm command is a convenient tool to resize various
types of filesystems. You could also use one of the tools
for your specific filesystem. Fedora Server uses xfs, IIRC,
so xfs_growfs would be that tool. For ext{2,3,4}, you can
use the resize2fs tool.
I'd use fsadm for its simplicity here. And even better is
letting lvextend call it in the future. ;)
--
Todd
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
