Bug 1132058
Summary: | [SNAPSHOT]: If the snapshoted brick has xfs options set as part of its creation, they are not automount upon reboot | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Rahul Hinduja <rhinduja> | |
Component: | snapshot | Assignee: | Vijaikumar Mallikarjuna <vmallika> | |
Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> | |
Severity: | urgent | Docs Contact: | ||
Priority: | unspecified | |||
Version: | rhgs-3.0 | CC: | bbandari, rhs-bugs, smohan, ssamanta, storage-qa-internal, vmallika | |
Target Milestone: | --- | |||
Target Release: | RHGS 3.0.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | SNAPSHOT | |||
Fixed In Version: | glusterfs-3.6.0.28-1 | Doc Type: | Bug Fix | |
Doc Text: |
If the brick mount options contains '=' then anything after '=' was omitted.
For example mount option 'rw,noatime,allocsize=1MiB,noattr2' is parsed as 'rw,noatime,allocsize'. This is now fixed
|
Story Points: | --- | |
Clone Of: | ||||
: | 1132451 (view as bug list) | Environment: | ||
Last Closed: | 2014-09-22 19:45:36 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: | 1124583, 1132451, 1145090 |
Description
Rahul Hinduja
2014-08-20 14:51:29 UTC
We are persisting the mount options in the brickinfo file as below: root@rh1:~/workspace/git/glusterfs # cat /var/lib/glusterd/snaps/snap1/6d6c402060d24601901d1fdd8312a7e4/bricks/rh1\:-var-run-gluster-snaps-6d6c402060d24601901d1fdd8312a7e4-brick1-dir | grep 'mnt-opts' mnt-opts=rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc When glusterd parsing this file it reads mount options as below which is not a valid as allocsize requires a value: mnt-opts=rw,noatime,allocsize From the next '=' in the line everything is ignored. Patch posted upstream Patch submitted: https://code.engineering.redhat.com/gerrit/#/c/31226/ Verified with the build: glusterfs-3.6.0.28-1.el6rhs.x86_64 Before reboot: ============== [root@inception ~]# cat before_reboot* /dev/mapper/RHS_vg10-RHS_lv10 on /rhs/brick10 type xfs (rw,noatime,nodiratime,inode64) /dev/mapper/RHS_vg1-RHS_lv1 on /rhs/brick1 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc) /dev/mapper/RHS_vg1-2aad9ef4dc7244b0a9f3ddd90c13318e_0 on /var/run/gluster/snaps/2aad9ef4dc7244b0a9f3ddd90c13318e/brick1 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc,nouuid) [root@inception ~]# [root@inception ~]# cat after_reboot* /dev/mapper/RHS_vg1-RHS_lv1 on /rhs/brick1 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc) /dev/mapper/RHS_vg10-RHS_lv10 on /rhs/brick10 type xfs (rw,noatime,nodiratime,inode64) /dev/mapper/RHS_vg1-2aad9ef4dc7244b0a9f3ddd90c13318e_0 on /var/run/gluster/snaps/2aad9ef4dc7244b0a9f3ddd90c13318e/brick1 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc,nouuid) [root@inception ~]# Brick is mounter after reboot: [root@inception ~]# mount | grep /var/run /dev/mapper/RHS_vg1-2aad9ef4dc7244b0a9f3ddd90c13318e_0 on /var/run/gluster/snaps/2aad9ef4dc7244b0a9f3ddd90c13318e/brick1 type xfs (rw,noatime,allocsize=1MiB,noattr2,barrier,nogrpid,ihashsize=0,noikeep,inode64,largeio,logbufs=4,noalign,nouuid,osyncisosync,quota,gquota,swalloc,nouuid) [root@inception ~]# Moving the bug to verified state. 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. http://rhn.redhat.com/errata/RHEA-2014-1278.html |