Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionChristopher Bradshaw
2022-08-10 18:01:52 UTC
Description of problem:
Filesystems(commented in fstab) are getting mounted after activating the volume group or logical volume via vgchange or lvchange (due to systemd unit files not updating).
This is a request for additional documentation in the manual pages and a clearer KCS or Article (easier to find online).
Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7
How reproducible:
Every time.
Steps to Reproduce:
1.) Umount and comment out a filesystem:
$ umount /mnt/test
$ grep test /etc/fstab
#/dev/mapper/vgtest-lvtest /mnt/test xfs defaults,nodev,nobarrier 0 0
2.) Deactivate Volume Group and then Activate Volume Group:
$ vgchange -an vgtest
0 logical volume(s) in volume group "vgtest" now active
0 logical volume(s) in volume group "vgtest" now active
$ vgchange -ay vgtest
4 logical volume(s) in volume group "vgtest" now active
Actual results:
The commented out filesystem is still automatically mounted (due to systemd unit file not being updated):
$ df -k | grep lvtest
/dev/mapper/vgtest-lvtest 2086912 32944 2053968 2% /mnt/test
Expected results:
Customer expects the commented filesystem to not be automatically mounted when activating the Volume Group. The customer understands that this is due to systemd unit files not being updated without reboot or systemctl daemon-reload.
This is really a request for additional documentation by Red Hat (i.e. manual pages updated for vgchange/lvchange/systemd).
Additional info:
Customer is asking for clearer documentation in the manual pages for vgchange, lvchange, lvm, and systemd. Customer now understand that this is due to the systemd unit not being updated - and the need to run:
$ systemctl daemon-reload
Reference Red Hat KCS:
https://access.redhat.com/solutions/3059631
Comment 3Christopher Bradshaw
2022-08-12 17:54:15 UTC
NOTE: I submitted this request for additional documentation for RHEL 7.* but think this would be a good addition for all versions >RHEL 7.0 (using systemd).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (util-linux bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:7186
Description of problem: Filesystems(commented in fstab) are getting mounted after activating the volume group or logical volume via vgchange or lvchange (due to systemd unit files not updating). This is a request for additional documentation in the manual pages and a clearer KCS or Article (easier to find online). Version-Release number of selected component (if applicable): Red Hat Enterprise Linux 7 How reproducible: Every time. Steps to Reproduce: 1.) Umount and comment out a filesystem: $ umount /mnt/test $ grep test /etc/fstab #/dev/mapper/vgtest-lvtest /mnt/test xfs defaults,nodev,nobarrier 0 0 2.) Deactivate Volume Group and then Activate Volume Group: $ vgchange -an vgtest 0 logical volume(s) in volume group "vgtest" now active 0 logical volume(s) in volume group "vgtest" now active $ vgchange -ay vgtest 4 logical volume(s) in volume group "vgtest" now active Actual results: The commented out filesystem is still automatically mounted (due to systemd unit file not being updated): $ df -k | grep lvtest /dev/mapper/vgtest-lvtest 2086912 32944 2053968 2% /mnt/test Expected results: Customer expects the commented filesystem to not be automatically mounted when activating the Volume Group. The customer understands that this is due to systemd unit files not being updated without reboot or systemctl daemon-reload. This is really a request for additional documentation by Red Hat (i.e. manual pages updated for vgchange/lvchange/systemd). Additional info: Customer is asking for clearer documentation in the manual pages for vgchange, lvchange, lvm, and systemd. Customer now understand that this is due to the systemd unit not being updated - and the need to run: $ systemctl daemon-reload Reference Red Hat KCS: https://access.redhat.com/solutions/3059631