[Bugs] [Bug 1256702] New: remove-brick: avoid mknod op falling on decommissioned brick even after fix-layout has happened on parent directory
bugzilla at redhat.com
bugzilla at redhat.com
Tue Aug 25 09:54:09 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1256702
Bug ID: 1256702
Summary: remove-brick: avoid mknod op falling on decommissioned
brick even after fix-layout has happened on parent
directory
Product: GlusterFS
Version: 3.7.3
Component: distribute
Assignee: bugs at gluster.org
Reporter: spalai at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com,
rgowdapp at redhat.com
Depends On: 1256243
+++ This bug was initially created as a clone of Bug #1256243 +++
Description of problem:
Because of stale-layout issue, a mknod op may fall on decommissioned brick even
after the parent layout is fixed.
Version-Release number of selected component (if applicable):
How reproducible:
Quite frequent with nfs mount
Steps to Reproduce:
1. create distribute volume with more than one brick
2. remove one of the brick
3. post remove-brick do large number of mknod call.
Actual results:
Some files are left on the removed-brick post remove-brick commit.
--- Additional comment from Anand Avati on 2015-08-25 13:53:51 MVT ---
COMMIT: http://review.gluster.org/11998 committed in master by Raghavendra G
(rgowdapp at redhat.com)
------
commit 90c7c30c3aa9417793ae972b2b9051bc5200e7e4
Author: Susant Palai <spalai at redhat.com>
Date: Mon Aug 24 03:04:41 2015 -0400
cluster/dht: avoid mknod on decommissioned brick
Change-Id: I8c39ce38e257758e27e11ccaaff4798138203e0c
BUG: 1256243
Signed-off-by: Susant Palai <spalai at redhat.com>
Reviewed-on: http://review.gluster.org/11998
Tested-by: NetBSD Build System <jenkins at build.gluster.org>
Tested-by: Gluster Build System <jenkins at build.gluster.com>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1256243
[Bug 1256243] remove-brick: avoid mknod op falling on decommissioned brick
even after fix-layout has happened on parent directory
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list