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. - Will -----Original Message----- From: krishna.zresearch at gmail.com [mailto:krishna.zresearch at gmail.com] On Behalf Of Krishna Srinivas Sent: Thursday, October 09, 2008 11:53 PM To: Will Rouesnel Cc: gluster-users at gluster.org Subject: Re: How to debug unify self-heal ? Will, What problem are you facing? If you could tell that we can fix it. The problem can be as simple as incorrect spec file. Regards Krishna On Wed, Oct 8, 2008 at 1:24 PM, Will Rouesnel <electricitylikesme at hotmail.com> wrote: > My ongoing saga in trying to get unify to work consistently across all > my files - does anyone know what the best way to debug the file > accesses going on on my bricks would be? Running glusterfs in debug > mode doesn't appear to yield any useful information - what's > concerning me is I can't tell whether gluster tries to access the > files on the brick and fails (and hence doesn't show them up in the > unify view) and if that's the case, at what level is it failing? > > - Will > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > >
