From: Gordan B. <go...@bo...> - 2009-12-25 01:14:19
|
On 23/07/2009 14:53, Gordan Bobic wrote: > On Thu, 23 Jul 2009 15:27:22 +0200, Marc Grimme<gr...@at...> wrote: >> Gordan, >> hardware-lib.sh -> upstream >> clusterfs-lib.sh ;-) >> + >> + >> > ############################################################################# >> + # GlusterFS settle time bug bodge! >> + sleep 5 >> + ls -la ${mountpoint}> /dev/null >> + ls -la ${mountpoint}/${prefix}> /dev/null >> + >> > ############################################################################# >> + >> >> I simply cannot do this. > > I know, it's horrible. > >> I could add a sleep with a timeout defaults 0 but which can be > overwritten >> as bootparameter. > > Yes, I guess that would be fine. > >> But do you really need those ls? > > I suspect that those aren't necessary any more with the latest version of > GlusterFS. There used to be a bug that caused first post-mounting access to > always fail, but I think this has been fixed now. > > The simple fact is that it is a GlusterFS issue, not an OSR issue, so I > fully understand the justification for not including this horrible > workaround at all. I only bothered posting it because there was no fix time > given. Just an update/confirmation - it looks like the problem requiring this workaround has been fixed in gluster since at least 2.0.8 (current version at the moment is 2.0.9). Those horrible "ls" lines aren't needed any more. :) But since they were never included in clusterfs-lib.sh, I guess it doesn't really matter. ;) Gordan |