Bug 1456420 - Restarting FUSE causes previous FUSE mounts to be in a bad state.
Summary: Restarting FUSE causes previous FUSE mounts to be in a bad state.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: fuse
Version: rhgs-3.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.2.0 Async
Assignee: Amar Tumballi
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On: 1424680
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-29 11:25 UTC by Atin Mukherjee
Modified: 2020-12-14 08:46 UTC (History)
33 users (show)

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).
Clone Of: 1424680
Environment:
Last Closed: 2017-06-08 09:37:05 UTC
Embargoed:
atumball: needinfo+
divya: needinfo+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1418 0 normal SHIPPED_LIVE glusterfs bug fix update 2017-06-08 13:33:58 UTC

Comment 4 Atin Mukherjee 2017-05-29 12:56:13 UTC 
downstream patches:

https://code.engineering.redhat.com/gerrit/#/c/107572/
https://code.engineering.redhat.com/gerrit/#/c/107573/
Comment 5 Amar Tumballi 2017-05-29 17:49:58 UTC 
Humble, help out in Doc Text. Need better wordings. Lets discuss and finalize tomorrow.
Comment 7 Praveen Varma 2017-05-30 06:27:21 UTC 
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
Comment 11 Divya 2017-06-06 13:46:15 UTC 
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
Comment 12 Amar Tumballi 2017-06-07 06:55:16 UTC 
Ack on content.

If we have not mentioned any other 'mount.glusterfs' options, then there is no need for documenting this.
Comment 14 errata-xmlrpc 2017-06-08 09:37:05 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.