Bug 762762 (GLUSTER-1030) - mount directory is not unmounted after killing glusterfs process
Summary: mount directory is not unmounted after killing glusterfs process
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1030
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-25 10:18 UTC by Raghavendra Bhat
Modified: 2015-12-01 16:45 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Amar Tumballi 2010-06-25 07:25:38 UTC 
This is happening after the changes in mainline due to dynamic volumes, and the different way of signal handling. There is also problem with running mainline code in gdb as SIGINT is getting messed up..
Comment 1 Csaba Henk 2010-06-25 07:38:53 UTC 
Cf bug #762733.
Comment 2 Raghavendra Bhat 2010-06-25 10:18:18 UTC 
After killing the glusterfs process mount point is not unmounted. Doing df says "Transport end-point is not connected" and have to be unmounted manually.
Comment 3 Vijay Bellur 2010-08-30 07:23:56 UTC 
PATCH: http://patches.gluster.com/patch/4372 in master (glusterfsd: call fini of fuse and all active xlators in cleanup_and_exit())
Comment 4 Vijay Bellur 2010-08-31 04:07:02 UTC 
PATCH: http://patches.gluster.com/patch/4406 in master (fix a crash in cleanup_and_exit ())
Note You need to log in before you can comment on or make changes to this bug.