Re: [Users] Attach nfs domain to gluster dc
Hi,
I'm finally starting to pis off with ovirt 100 steps and locks. As I
can't modify the export domain while it's in maintenance and while it's
active I can't change the version, how should I get rid of the v3
limitation on this existing domain?
Can someone tell me why ovirt defaults v3 and not 4? is it something to
do with existing bugs or limitations?
Can you please put as much energy in make things easier as you put in
new features? Not a critic but a request.
Regards,
On 11/12/13 10:08, Dan Kenigsberg wrote:
On Tue, Dec 10, 2013 at 05:10:55PM -0200, Juan Pablo Lorier wrote:
> Hi,
>
> I've created a new DC in order of been able to create vms on a glusterfs
> data domain. As ovirt does not allow to share export and iso domains
> between DCs (nice RFE) I detach those from the actual DC and when I try
> to attach them to the new DC, I get an error:
>
> 2013-12-10 15:19:28,558 ERROR
> [org.ovirt.engine.core.bll.storage.NFSStorageHelper] (pool-6-thread-46)
> The connection with details 192.168.128.81:/home/exports/export failed
> because of error code 477 and error message is: problem while trying to
> mount target
> 2013-12-10 15:19:28,577 ERROR
> [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand]
> (pool-6-thread-46) Transaction rolled-back for command:
> org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand.
> 2013-12-10 15:19:28,578 ERROR
> [org.ovirt.engine.core.bll.storage.NFSStorageHelper] (pool-6-thread-41)
> The connection with details 192.168.128.81:/home/exports/export failed
> because of error code 477 and error message is: problem while trying to
> mount target
> 2013-12-10 15:19:28,587 ERROR
> [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand]
> (pool-6-thread-41) Transaction rolled-back for command:
> org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand.
>
> But if I mount the nfs share manually from the hosts, I have no problems.
> I've been having issues with nfs since I updated to 3.3.1, I have the
> nfs shares in one of the hosts of the iscsi domain and the other host
> complaints about not been ablo to access the domains from time to time.
> The host where the shares are never complaints.
> Any hints?
> Regards,
Could you provide the exact mount command line, and its error response,
from supervdsm/vdsm.log?