No
On Thu, Aug 16, 2012 at 10:39 AM, Keith Robertson <kroberts(a)redhat.com> wrote:
On 08/16/2012 11:31 AM, Brent Bolin wrote:
>
> I was not doing any of this from the hypervisor :)
>
> Guess I'm a little confused how all this works. Was doing this from
> the Ovirt engine
>
> I get this when I try to mount -
>
> mount -t nfs 192.168.0.61:/vm/iso /mnt/test
> 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
>
> Its mountable if I use the -o nolock switch
Just a shot in the dark, but do you have a firewall running on the NFS
server? If so it could be blocking that port.
>
> On Thu, Aug 16, 2012 at 9:47 AM, Keith Robertson <kroberts(a)redhat.com>
> wrote:
>>
>> On 08/16/2012 10:38 AM, Brent Bolin wrote:
>>>
>>> Anybody have any solutions to this. I'm getting this error and pretty
>>> much stuck from doing anything.
>>>
>>> ovirt-node-iso-2.5.1-1.0.fc17.iso
>>> Fedora 17 kernel 3.3.4-5.fc17.x86_64
>>> Ovirt 3.1
>>>
>>> Error 477 and 500 from the UI
>>>
>>> I've tried nfs3 and nfs4. I can manually mount either. And
>>> touch/remove files logged in as user vdsm
>>
>> I am assuming that you have attempted to mount the NFS export from the
>> hypervisor, correct?
>> 1- On the hypervisor mount the export as root: mount -t nfs <ip address
>> here>:/path/to/storagedomain /tmp/mountpt
>> 2- su - vdsm
>> 3- cd /tmp/mountpt/path/to/isodomain
>> 4- Try to add/remove a file as user 'vdsm'
>>
>>>
>>>
>>> On Tue, Aug 14, 2012 at 2:12 PM, Dominic Kaiser
>>> <dominic(a)bostonvineyard.org> wrote:
>>>>
>>>> Today I had the same error both 500 and 477. I was using
>>>> ovirt-node-iso-2.5.0-2.0.fc17. I was doing a new install of 3.1 and
>>>> could
>>>> not add NFS storage at all. This build has a pre 3.5 kernel on it so
>>>> that
>>>> should not have been the problem. I then installed a new copy of
>>>> Fedora
>>>> 17
>>>> as the node added it as a host and was able to add all my NFS domains.
>>>> I
>>>> hope that helps. And does anyone know of this node build having
>>>> problems?
>>>> I can replicate this issue.
>>>>
>>>> Dominic
>>>>
>>>> On Tue, Aug 14, 2012 at 10:27 AM, Ricardo Esteves
>>>> <ricardo.m.esteves(a)gmail.com> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> I'm trying to import an ISO domain, but i get this: Error: A
Request
>>>>> to
>>>>> the Server failed with the following Status Code: 500
>>>>>
>>>>> On vdsm log i have this:
>>>>>
>>>>> MountError: (32, ";mount.nfs: rpc.statd is not running but is
required
>>>>> for
>>>>> remote locking.\nmount.nfs: Either use '-o nolock' to keep
locks
>>>>> local,
>>>>> or
>>>>> start statd.\nmount.nfs: an incorrect mount option was
specified\n")
>>>>>
>>>>> Can someone help please?
>>>>>
>>>>> Best regards,
>>>>> Ricardo Esteves.
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users(a)ovirt.org
>>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>>
>>>>
>>>> --
>>>> Dominic Kaiser
>>>> Greater Boston Vineyard
>>>> Director of Operations
>>>>
>>>> cell: 617-230-1412
>>>> fax: 617-252-0238
>>>> email: dominic(a)bostonvineyard.org
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users(a)ovirt.org
>>>>
http://lists.ovirt.org/mailman/listinfo/users
>>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users(a)ovirt.org
>>>
http://lists.ovirt.org/mailman/listinfo/users
>>
>>