Filesystem cannot be extended after resizing LVM logical volume on another cluster node on Red Hat Enterprise Linux
Issue
The volume is seen on two machines, we expanded the volume on the node that did not have the volumegroup activated.
See output below.
Extend the LV on wrong machine.
[root@selxdb02 ~]# lvextend -i1 -l +38400 /dev/selxerpp01_data01_vg01/datavol01
Extending logical volume datavol01 to 750.00 GiB
Logical volume datavol01 successfully resized
[root@selxdb02 ~]# xfs_growfs /dev/selxerpp01_data01_vg01/datavol01
xfs_growfs: /dev/selxerpp01_data01_vg01/datavol01 is not a mounted XFS filesystem
So we tried to expand the filesystem on the node owning the filesystem at the moment.
[root@selxdb03 ~]# xfs_growfs /dev/selxerpp01_data01_vg01/datavol01
meta-data=/dev/mapper/selxerpp01_data01_vg01-datavol01 isize=256 agcount=33, agsize=4915184 blks
= sectsz=512 attr=2
data = bsize=4096 blocks=157286400, imaxpct=25
= sunit=16 swidth=32 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal bsize=4096 blocks=76800, version=2
= sectsz=512 sunit=16 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
But it wont expand to the correct size.
Environment
- Red Hat Enterprise Linux (RHEL), including:
- Red Hat Cluster Suite 4+
- Red Hat Enterprise Linux Server 5 (with the High Availability Add on)
- Red Hat Enterprise Linux Server 6 (with the High Availability Add on)
- Shared storage available on 2 or more cluster nodes
- LVM volume management on shared storage
- Resized LVM logical volume on a backup node, but received an error trying to resize the filesystem on the active node
- All resizable filesystems are affected by this issue including ext2, ext3, ext4, gfs, gfs2 and xfs.
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.