There is a known bug for this : http://bugs.gluster.com/show_bug.cgi?id=1203 <http://bugs.gluster.com/show_bug.cgi?id=1203>Recently Jeff Darcy also filed a bug in same context of above bug : http://bugs.gluster.com/show_bug.cgi?id=3085 <http://bugs.gluster.com/show_bug.cgi?id=3085>(He also submitted a patch). As a work around for mount.glusterfs issue, the below patch should give minimal remedy. http://patches.gluster.com/patch/7796/ A proper fix will be available in future versions within all glusterfs binary itself. Regards, Amar On Mon, Jul 11, 2011 at 5:58 PM, Marco Agostini <comunelevico at gmail.com>wrote: > 2011/7/11 Darren Austin <darren-lists at widgit.com>: > > > > I had noticed the same thing, and intended to post a note about it too :) > > > > The way I worked around this issue is to use the "mountpoint" command > directly after the mount. > > Eg: > > > > mount -t glusterfs server:volume /mnt > > mountpoint /mnt > > echo $? > > > > ... will do what you want :) > > > Yea, great... is exactly wath I want, thanks. > > I have write a post here > http://community.gluster.org/p/bash-exit-code-when-mount-command-failed/ > > thank you. > _______________________________________________ > 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/20110711/1c0c3ced/attachment.htm>
