Bug 764913 (GLUSTER-3181) - object-storage: stale mount after volume re-creation should be known to system
Summary: object-storage: stale mount after volume re-creation should be known to system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3181
Product: GlusterFS
Classification: Community
Component: object-storage
Version: pre-release
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Gaurav
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-16 13:01 UTC by Saurabh
Modified: 2011-09-19 05:05 UTC (History)
1 user (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)

Description Saurabh 2011-07-16 13:01:28 UTC
scenario is,
1. create a volume, eg. distribute-replicate
2. start it
3. put some data in it using object-storage.
expected here during step 3 is that a fuse mount will get created automatically and this happens properly
4. now stop/delete the volume, but don't umount the earlier created mount
5. re-create the volume with same name, using the same back-end.
6. now try to create the data using curl. 

Now, as per present scenario it fails, as the mount that is already is stale, and swift integration does not get to know and does not try to create a new mount. 

Please check this can be fixed.

Comment 1 Saurabh 2011-09-19 02:05:52 UTC
wht is the fix or thought behind resolution?


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