Bug 1456420
| Summary: | Restarting FUSE causes previous FUSE mounts to be in a bad state. | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Atin Mukherjee <amukherj> |
| Component: | fuse | Assignee: | Amar Tumballi <atumball> |
| Status: | CLOSED ERRATA | QA Contact: | Rahul Hinduja <rhinduja> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | rhgs-3.2 | CC: | akhakhar, amarts, amukherj, annair, atumball, bchilds, bmekala, cmaiolin, csaba, divya, eguan, eparis, hchen, hchiramm, jarrpa, kramdoss, madam, mchangir, mliyazud, mrobson, myllynen, mzywusko, pdwyer, pprakash, pvarma, rcyriac, rhinduja, rhs-bugs, rreddy, rtalur, storage-qa-internal, tlarsson, zlang |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | RHGS 3.2.0 Async | Flags: | atumball:
needinfo+
divya: needinfo+ |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.8.4-18.3 | Doc Type: | Enhancement |
| Doc Text: |
Gluster's FUSE mount process can now process 'auto_unmount' flag. With this new mount option, Gluster FUSE mount process will not leave a 'stale mount point', in case the client process terminates abnormally (like SIGTERM, SIGSEGV, and so on).
|
Story Points: | --- |
| Clone Of: | 1424680 | Environment: | |
| Last Closed: | 2017-06-08 09:37:05 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: | 1424680 | ||
| Bug Blocks: | |||
|
Comment 4
Atin Mukherjee
2017-05-29 12:56:13 UTC
Humble, help out in Doc Text. Need better wordings. Lets discuss and finalize tomorrow. To let you know, there is an ICE that I am handling which is associated to this BZ and customer would absolutely like to know when the QA would be done and when the release would happen as they are eagerly waiting. Can one of you please comment and give an ETA? Thanks, Praveen Escalation manager Thanks Humble! Amar, Could you please review and sign-off the edited doc text? Also, should we document this mount option in the Admin guide [1]? [1] https://access.qa.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/administration_guide/#sect-Mounting_Red_Hat_Storage_Volumes Ack on content. If we have not mentioned any other 'mount.glusterfs' options, then there is no need for documenting this. 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:1418 |