9:28 a.m.
We still not have moved to 4.3 (4.2.8 atm)
<lan storage/server>(rw,no_subtree_check,insecure,no_root_squash)
with -w it does :
rw,sync,wdelay,hide,no_subtree_check,sec=sys,insecure,no_root_squash,no_all_squash
(not at all nfs expert, but it's one of the rare setup working for me...
if ever someone see a problem, please point it :)
Cordialement,
Alexis Grillon
Pôle Humanités Numériques, Outils, Méthodes et Analyse de Données
Maison européenne des sciences de l'homme et de la société
MESHS - Lille Nord de France / CNRS
tel. +33 (0)3 20 12 58 57 | alexis.grillon(a)meshs.fr
www.meshs.fr | 2, rue des Canonniers 59000 Lille
-----------------------------------------------------------------
GPG fingerprint AC37 4C4B 6308 975B 77D4 772F 214F 1E97 6C08 CD11
Le 13/02/2019 à 16:02, Arman Khalatyan a écrit :
/data on ZoL exported with nfs4:
(rw,sync,all_squash,no_subtree_check,anonuid=36,anongid=36)
Centos7.6, oVirt 4.2.8, ovirt-engine runs on a bare metal
On Wed, Feb 13, 2019 at 3:17 PM Torsten Stolpmann
<torsten.stolpmann(a)verit.de> wrote:
>
> /etc/exports:
>
> /export/volumes *(rw,all_squash,anonuid=36,anongid=36)
>
>
> exportfs -v:
>
> /data/volumes
>
<world>(sync,wdelay,hide,no_subtree_check,anonuid=36,anongid=36,sec=sys,rw,secure,root_squash,all_squash)
>
> Centos7.6, oVirt 4.2.8. We are not running HE, ovirt-engine runs on bare
> metal. Not sure if this information is relevant then.
>
> Torsten
>
> On 12.02.2019 23:39, Nir Soffer wrote:
>> Looking at
>> https://bugzilla.redhat.com/1666795
>>
>> It seems that a change in vdsm/libvirt exposed NFS configuration issue,
>> that may was
>> needed in the past and probably not needed now.
>>
>> If you use NFS, I would like to see your /etc/exports (after sanitizing
>> it if needed).
>> For extra bonus, output of "exportfs -v" would be useful.
>>
>> In particular, I want to know if you use root_squash, all_squash, or
>> no_root_squash.
>>
>> Thanks,
>> Nir
>>
>> _______________________________________________
>> Users mailing list -- users(a)ovirt.org
>> To unsubscribe send an email to users-leave(a)ovirt.org
>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
>> oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
>> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/7J3ZV25DP2X...
>>
> _______________________________________________
> Users mailing list -- users(a)ovirt.org
> To unsubscribe send an email to users-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
> List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/3JLCVXS72DT...
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/JYQEPGP5CHO...