Bug 762325 (GLUSTER-593) - Not able to mount after update
Summary: Not able to mount after update
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-593
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-04 14:29 UTC by Raghavendra Bhat
Modified: 2010-02-07 22:47 UTC (History)
2 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 Raghavendra Bhat 2010-02-04 14:29:52 UTC 
After update was clicking under volume parameters the glusterfs client cannot be mounted. It gives transport end-point not connected.

After checking the volume files on the server it was seen that glusterfs server daemon was not restarted at all after the volume updation and it was running in an old port. 

Volume files were reflecting 10004 but the netstat -ntlp yielded that glusterfs daemon was running at 10002 port.
Comment 1 Balamurugan Arumugam 2010-02-07 19:47:58 UTC 
This is required behavior that remounting should be done at client side after restarting volume.
Note You need to log in before you can comment on or make changes to this bug.