Thanks for your kindly reply, but I think the problem may not be glusterfs , i have tested with a normal nfs storage, the error still the same. There's familiar case in ' http://comments.gmane.org/gmane.comp.emulators.ovirt.user/3216 ' , says:
It seems it's related http://gerrit.ovirt.org/#/c/4720/. The unnecessary nfs related rpm/commands including rpc-bind were removed from ovirt-node. But the service nfs-lock requires rpc-bind, so it can't start. I guess so. Michael, is it? Thanks!
seems the problem has occurred since ovirt-node-iso-2.5.0-2.0.fc17 and related with this merge. On 24 Jan, 2013, at 2:50 AM, Vijay Bellur <vbellur@redhat.com> wrote:
On 01/22/2013 03:28 PM, T-Sinjon wrote:
HI, everyone: Recently , I newly installed ovirt 3.1 from http://resources.ovirt.org/releases/stable/rpm/Fedora/17/noarch/, and node use http://resources.ovirt.org/releases/stable/tools/ovirt-node-iso-2.5.5-0.1.fc...
when i add gluster domain via nfs, mount error occurred, I have do manually mount action on the node but failed if without -o nolock option: # /usr/bin/mount -t nfs -o soft,nosharecache,timeo=600,retrans=6 my-gluster-ip:/gvol02/GlusterDomain /rhev/data-center/mnt/my-gluster-ip:_gvol02_GlusterDomain mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: an incorrect mount option was specified
Can you please confirm the glusterfs version that is available in ovirt-node-iso?
Thanks, Vijay