Bug 1500720
| Summary: | Gluster Volume restart fail after exporting fuse sub-dir | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Manisha Saini <msaini> | |
| Component: | fuse | Assignee: | Amar Tumballi <atumball> | |
| Status: | CLOSED ERRATA | QA Contact: | Manisha Saini <msaini> | |
| Severity: | urgent | Docs Contact: | ||
| Priority: | urgent | |||
| Version: | rhgs-3.3 | CC: | amukherj, asrivast, rcyriac, rhinduja, rhs-bugs, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | RHGS 3.3.1 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.8.4-50 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1501315 (view as bug list) | Environment: | ||
| Last Closed: | 2017-11-29 03:30: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: | 1475688 | |||
|
Description
Manisha Saini
2017-10-11 11:32:57 UTC
Upstream patch to fix the issue is at : https://review.gluster.org/#/c/18489/ This is a blocker for Subdir mount feature, hence requesting for Acks! Verified this bug with glusterfs-3.8.4-50.el7rhgs.x86_64. Steps: 1.Create 4*3 Distributed-Replicate volume. 2.Mount the volume on client via fuse # mount -t glusterfs dhcp42-125.lab.eng.blr.redhat.com:ganeshavol2/ /mnt/volume_mount1 3.Create sub-dir inside mount point [root@dhcp37-192 volume_mount1]# ls [root@dhcp37-192 volume_mount1]# mkdir dir1 4.Set permissions on volume for the subdir # gluster v set ganeshavol2 auth.allow "/dir1(10.70.37.192),/(*)" volume set: success 5.Mount the sub-dir on client [root@dhcp37-192 mnt]# mount -t glusterfs dhcp42-125.lab.eng.blr.redhat.com:ganeshavol2/dir1 /mnt/sub-dir2 [root@dhcp37-192 mnt]# cd /mnt/sub-dir2 [root@dhcp37-192 sub-dir2]# ls [root@dhcp37-192 sub-dir2]# touch f1 [root@dhcp37-192 sub-dir2]# touch f2 [root@dhcp37-192 sub-dir2]# touch f3 [root@dhcp37-192 sub-dir2]# mkdir dir1 [root@dhcp37-192 sub-dir2]# mkdir dir2 [root@dhcp37-192 sub-dir2]# mkdir dir3 6.Do volume stop and start.Check volume status. [root@dhcp42-125 brick4]# gluster v stop ganeshavol2 Stopping volume will make its data inaccessible. Do you want to continue? (y/n) y volume stop: ganeshavol2: success [root@dhcp42-125 brick4]# gluster v start ganeshavol2 volume start: ganeshavol2: success [root@dhcp42-125 brick4]# gluster v status ganeshavol2 Status of volume: ganeshavol2 Gluster process TCP Port RDMA Port Online Pid ------------------------------------------------------------------------------ Brick dhcp42-125.lab.eng.blr.redhat.com:/gl uster/brick4/2 49155 0 Y 10875 Brick dhcp42-127.lab.eng.blr.redhat.com:/gl uster/brick4/2 49155 0 Y 27736 Brick dhcp42-129.lab.eng.blr.redhat.com:/gl uster/brick4/2 49155 0 Y 29969 Brick dhcp42-119.lab.eng.blr.redhat.com:/gl uster/brick4/2 49155 0 Y 28521 Brick dhcp42-125.lab.eng.blr.redhat.com:/gl uster/brick5/2 49156 0 Y 10894 Brick dhcp42-127.lab.eng.blr.redhat.com:/gl uster/brick5/2 49156 0 Y 27755 Brick dhcp42-129.lab.eng.blr.redhat.com:/gl uster/brick5/2 49156 0 Y 29988 Brick dhcp42-119.lab.eng.blr.redhat.com:/gl uster/brick5/2 49156 0 Y 28540 Brick dhcp42-125.lab.eng.blr.redhat.com:/gl uster/brick6/2 49157 0 Y 10913 Brick dhcp42-127.lab.eng.blr.redhat.com:/gl uster/brick6/2 49157 0 Y 27774 Brick dhcp42-129.lab.eng.blr.redhat.com:/gl uster/brick6/2 49157 0 Y 30007 Brick dhcp42-119.lab.eng.blr.redhat.com:/gl uster/brick6/2 49157 0 Y 28559 Self-heal Daemon on localhost N/A N/A Y 10933 Self-heal Daemon on dhcp42-127.lab.eng.blr. redhat.com N/A N/A Y 27794 Self-heal Daemon on dhcp42-129.lab.eng.blr. redhat.com N/A N/A Y 30027 Self-heal Daemon on dhcp42-119.lab.eng.blr. redhat.com N/A N/A Y 28579 Task Status of Volume ganeshavol2 ------------------------------------------------------------------------------ There are no active volume tasks 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-2017:3276 |