Bug 762552 (GLUSTER-820) - distribute directory rename problem when one subvol is down
Summary: distribute directory rename problem when one subvol is down
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-820
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra Bhat
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-13 17:33 UTC by Krishna Srinivas
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

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

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

Description Krishna Srinivas 2010-04-13 17:33:04 UTC 
distribute: directory rename creates problem when one subvol is down. i.e when the subvol comes back up old directory is seen and when we do rm -rf on it we can get ENOEMPTY because of existing subdirs on only that subvolume. (ticket 1781)

do not allow dir renames when one of the subvol is down or do a "restore" operation when rename fails on one subvol.
Comment 1 Anand Avati 2010-05-08 10:37:19 UTC 
PATCH: http://patches.gluster.com/patch/3227 in master (Check whether a server is down before calling rename on the directory)
Comment 2 Anand Avati 2010-05-08 10:37:49 UTC 
PATCH: http://patches.gluster.com/patch/3226 in release-3.0 (Check whether a server is down before calling rename on the directory)
Comment 3 Raghavendra Bhat 2010-06-08 03:10:09 UTC 
Checked with 3.0.5rc4 and 3.0.5rc5. It has been fixed. Directory cannot be renamed when one of the servers is dowm.
Note You need to log in before you can comment on or make changes to this bug.