Bug 762559 (GLUSTER-827) - distribute directory selfheal is wrongly triggered
Summary: distribute directory selfheal is wrongly triggered
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-827
Product: GlusterFS
Classification: Community
Component: distribute
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-16 23:47 UTC by Krishna Srinivas
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 Krishna Srinivas 2010-04-16 23:47:06 UTC 
Steps:
* distribute subvol list is expanded
* access directory from mount point
* selfheal gets triggered causing reassignment of hash ranges.
* this causes a lot of unnecessary links files to be created when files are accessed from the mount point. If option lookup-unhashed is auto, it can result in creation of duplicate file names. refer to bug 762558
Comment 1 Amar Tumballi 2010-05-07 04:08:15 UTC 
> * selfheal gets triggered causing reassignment of hash ranges.
> * this causes a lot of unnecessary links files to be created when files are
> accessed from the mount point. If option lookup-unhashed is auto, it can result
> in creation of duplicate file names. refer to bug 762558

Hi Kr1s, IMO this patch : http://patches.gluster.com/patch/3176/ fixes the problem. Let me know if we can close this bug.
Comment 2 Krishna Srinivas 2010-05-07 13:14:59 UTC 
(In reply to comment #1)
> > * selfheal gets triggered causing reassignment of hash ranges.
> > * this causes a lot of unnecessary links files to be created when files are
> > accessed from the mount point. If option lookup-unhashed is auto, it can result
> > in creation of duplicate file names. refer to bug 762558
> 
> Hi Kr1s, IMO this patch : http://patches.gluster.com/patch/3176/ fixes the
> problem. Let me know if we can close this bug.

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