Looking at the first mail in the thread, after 'creating' the volume, you are trying to mount it.. please run 'gluster volume start kvm' before running mount. If you have already done it, check if actually the brick process (glusterfsd) is still running by 'ps ax | grep glusterfsd' on server. If not, please go through the brick log file for more information. I suspect that the brick here can be a read-only backend which would have killed glusterfsd process even when you do 'gluster volume start'. Regards, Amar On Thu, May 12, 2011 at 5:46 AM, Chris Haumesser <ch at luciddg.com> wrote: > Replying to my own thread ... > > After reading more mailing list archives and docs, I tried disabling > stat-prefetch, to no avail. > > I next disabled all of the other performance-related features > (write-behind, read-ahead, io-cache, quick-read), and now my debootstrap > appears to be (albeit slowly) going about its business without issue. > > I also noticed that 42 seconds is the default value for > network.ping-timeout, which corresponds to the error I was seeing in syslog. > > > Which of the above options, now disabled, is most likely to have triggered > the network ping timeouts that I was consistently seeing before? (I did not > change anything on the network.) > > What other side-effects and performance hits will I incur with the above > options disabled? > > Finally, I do not see descriptions of what the io-cache or quick-read > options do in the 3.2 docs. Can someone elucidate? I would also love more > thorough explanations of what how write-behind and read-ahead work (the docs > are pretty terse). > > Thanks everyone. > > Cheers, > > > -C- > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20110523/47e06ccc/attachment.htm>
