Bug 1649509
| Summary: | fstab entries are updated even for bricks on non-VDO volumes | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | SATHEESARAN <sasundar> | ||||
| Component: | gdeploy | Assignee: | Sachidananda Urs <surs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | rhhiv-1.5 | CC: | pmulay, rcyriac, rhs-bugs, sabose, sankarshan, smohan, storage-qa-internal, surs | ||||
| Target Milestone: | --- | Keywords: | ZStream | ||||
| Target Release: | RHGS 3.4.z Batch Update 2 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | gdeploy-2.0.2-31 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Previously, non-VDO devices failed to mount due to mount options specific to VDO. This update ensures that the mount options are set appropriately for VDO and non-VDO disks leading to a successful mount.
|
Story Points: | --- | ||||
| Clone Of: | 1649507 | Environment: | |||||
| Last Closed: | 2018-12-17 17:07:34 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1649507 | ||||||
| Attachments: |
|
||||||
|
Description
SATHEESARAN
2018-11-13 18:35:41 UTC
Created attachment 1505399 [details]
gdeploy conf file used to create VDO & non-VDO volumes
Patch posted for review: https://github.com/gluster/gdeploy/pull/519 Tested with gdeploy-2.0.2-31.el7rhgs Additional mount options (_netdev,x-systemd.device-timeout=0,x-systemd.requires=vdo.service) are updated with /etc/fstab for XFS filesystems ( gluster bricks ) created on top of VDO volumes The other XFS filesystems created on disks ( not on VDO volumes ) doesn't have VDO special options <snip> /dev/gluster_vg_sdb/gluster_lv_engine /gluster_bricks/engine xfs inode64,noatime,nodiratime 0 0 /dev/gluster_vg_sdc/gluster_lv_data /gluster_bricks/data xfs inode64,noatime,nodiratime,_netdev,x-systemd.device-timeout=0,x-systemd.requires=vdo.service 0 0 /dev/gluster_vg_sdc/gluster_lv_vmstore /gluster_bricks/vmstore xfs inode64,noatime,nodiratime,_netdev,x-systemd.device-timeout=0,x-systemd.requires=vdo.service 0 0 /dev/gluster_vg_sdd/gluster_lv_newvol /gluster_bricks/newvol xfs inode64,noatime,nodiratime 0 0 </snip> 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, 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-2018:3830 |