_____ From: Raghavendra G [mailto:raghavendra.hg at gmail.com] Sent: Friday, October 10, 2008 3:37 PM To: Will Rouesnel Cc: Krishna Srinivas; gluster-users at gluster.org Subject: Re: How to debug unify self-heal ? On Fri, Oct 10, 2008 at 7:36 AM, Will Rouesnel <electricitylikesme at hotmail.com> wrote: Periodically on my gluster setup, unify will fail to display the files that are some of the bricks. The only way I've found to correct this is to delete the containing directory from the glusterfs mount and then recopy it through the glusterfs mount. The files on the bricks themselves are fine and if I access them directly they are perfectly usable. What I can't work out, is what property of the files comes up that causes this behavior from unify. I'm not using AFR, and if I try to directly access the files then the unify log will generate an error indicating it found the file on the brick but not in the namespace. However if I list the contents of the directory, the file does not show up. Are the files which you cannot ls on glusterfs mount present on the namespace node? No they are not. I've tried deleting the namespace node and letting it rebuild, but for the files for which I have the problem this does not recreate them on the namespace node either. The thing is I can't find anything wrong with the files which would stop gluster from accessing them, nor any attributes it might be reacting to. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081010/984cdcb8/attachment.htm
