Bug 819466 - Killing a fuse client mounted using relative path leaves a stale moount
Summary: Killing a fuse client mounted using relative path leaves a stale moount
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: fuse
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Kaushal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 817967
TreeView+ depends on / blocked
 
Reported: 2012-05-07 10:36 UTC by Anush Shetty
Modified: 2013-07-24 18:01 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.4.0
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 18:01:13 UTC
Regression: ---
Mount Type: fuse
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Anush Shetty 2012-05-07 10:36:16 UTC
Description of problem: After mounting the fuse client with a relative path,killing the client process resulted in a stale mount


Version-Release number of selected component (if applicable): Upstream


How reproducible: Consistently


Expected results: There should be no stale mount.


Additional info:

Comment 1 Anand Avati 2012-05-09 00:00:26 UTC
CHANGE: http://review.gluster.com/3302 (glusterfsd: Make sure mountpoint is an absolute path) merged in master by Anand Avati (avati)

Comment 2 Anush Shetty 2012-05-09 09:44:08 UTC
Verified with git head 7b0814243b4ccd56c0ce570b7f42d5e572e1e71.


Note You need to log in before you can comment on or make changes to this bug.