Hi all, I am very new to IPA and still a bit before going into production, so apologies in advance.
The plan is to have a number of servers that each one shares a space via kerberized nfs4 to the others, which makes all of them NFS clients and servers at the same time. On my attempt to setup automount globally via IdM and sssd, I realized that when a machine is configured as nfs server, it needs autofs.service to be stopped in order to access it's local shares mounted via fstab. If I use /etc/auto.master to mount the local shares instead of fstab, then autofs.service may (actually must) run and everything works properly but, doing so, I don't have the advantage of one central configuration location any more. The preferred scenario for each server would be to mount its local shares via fstab and the remote shares via sssd automount. Am I missing something?
Thanks in advance, Petros
One easy way to resolve your issues it to use different names for the export location and the mount location. Your export location is handled by fstab, whereas your mount location is handled by autofs. For example, your have server1 with /export_data1 and server2 with /export_data2 mounted via fstab. NFS + autofs will mount them as /data1 and /data2 on all the clients including the NFS servers. Does this work for you ?
On Sun, Jul 2, 2017 at 1:58 PM, Petros Triantafyllidis via FreeIPA-users < freeipa-users@lists.fedorahosted.org> wrote:
Hi all, I am very new to IPA and still a bit before going into production, so apologies in advance.
The plan is to have a number of servers that each one shares a space via kerberized nfs4 to the others, which makes all of them NFS clients and servers at the same time. On my attempt to setup automount globally via IdM and sssd, I realized that when a machine is configured as nfs server, it needs autofs.service to be stopped in order to access it's local shares mounted via fstab. If I use /etc/auto.master to mount the local shares instead of fstab, then autofs.service may (actually must) run and everything works properly but, doing so, I don't have the advantage of one central configuration location any more. The preferred scenario for each server would be to mount its local shares via fstab and the remote shares via sssd automount. Am I missing something?
Thanks in advance, Petros
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org
Thanks a lot for replying, Yes, your suggestion is working. Doesn't seem that elegant though, since a partition is mounted several times. However it's practical and I can't figure out how else it could be done. From mount stats, the first two are from fstab mount and appears only on NFS server, while the third is the automount and appears on all NFS clients (NFS server included)
/dev/sdb1 on /export/data1 type xfs (rw,relatime,attr2,inode64,noquota) /dev/sdb1 on /data1 type xfs (rw,relatime,attr2,inode64,noquota) auto.direct on /data1 type autofs (rw,relatime,fd=18,pgrp=34091,timeout=300,minproto=5,maxproto=5,direct)
Thanks a lot, Petros
On 07/12/2017 01:11 AM, Prasun Gera via FreeIPA-users wrote:
One easy way to resolve your issues it to use different names for the export location and the mount location. Your export location is handled by fstab, whereas your mount location is handled by autofs. For example, your have server1 with /export_data1 and server2 with /export_data2 mounted via fstab. NFS + autofs will mount them as /data1 and /data2 on all the clients including the NFS servers. Does this work for you ?
On Sun, Jul 2, 2017 at 1:58 PM, Petros Triantafyllidis via FreeIPA-users <freeipa-users@lists.fedorahosted.org mailto:freeipa-users@lists.fedorahosted.org> wrote:
Hi all, I am very new to IPA and still a bit before going into production, so apologies in advance. The plan is to have a number of servers that each one shares a space via kerberized nfs4 to the others, which makes all of them NFS clients and servers at the same time. On my attempt to setup automount globally via IdM and sssd, I realized that when a machine is configured as nfs server, it needs autofs.service to be stopped in order to access it's local shares mounted via fstab. If I use /etc/auto.master to mount the local shares instead of fstab, then autofs.service may (actually must) run and everything works properly but, doing so, I don't have the advantage of one central configuration location any more. The preferred scenario for each server would be to mount its local shares via fstab and the remote shares via sssd automount. Am I missing something? Thanks in advance, Petros
The only thing I would be interested in knowing is if there is a performance penalty to mounting NFS locally. Ideally, it should be smart enough to know that, but I'm not sure if it is.
On 14 Jul 2017 6:08 pm, "Petros Triantafyllidis" trian@auth.gr wrote:
Thanks a lot for replying, Yes, your suggestion is working. Doesn't seem that elegant though, since a partition is mounted several times. However it's practical and I can't figure out how else it could be done. From mount stats, the first two are from fstab mount and appears only on NFS server, while the third is the automount and appears on all NFS clients (NFS server included)
/dev/sdb1 on /export/data1 type xfs (rw,relatime,attr2,inode64,noquota) /dev/sdb1 on /data1 type xfs (rw,relatime,attr2,inode64,noquota) auto.direct on /data1 type autofs (rw,relatime,fd=18,pgrp=34091, timeout=300,minproto=5,maxproto=5,direct)
Thanks a lot, Petros
On 07/12/2017 01:11 AM, Prasun Gera via FreeIPA-users wrote:
One easy way to resolve your issues it to use different names for the export location and the mount location. Your export location is handled by fstab, whereas your mount location is handled by autofs. For example, your have server1 with /export_data1 and server2 with /export_data2 mounted via fstab. NFS + autofs will mount them as /data1 and /data2 on all the clients including the NFS servers. Does this work for you ?
On Sun, Jul 2, 2017 at 1:58 PM, Petros Triantafyllidis via FreeIPA-users < freeipa-users@lists.fedorahosted.org> wrote:
Hi all, I am very new to IPA and still a bit before going into production, so apologies in advance.
The plan is to have a number of servers that each one shares a space via kerberized nfs4 to the others, which makes all of them NFS clients and servers at the same time. On my attempt to setup automount globally via IdM and sssd, I realized that when a machine is configured as nfs server, it needs autofs.service to be stopped in order to access it's local shares mounted via fstab. If I use /etc/auto.master to mount the local shares instead of fstab, then autofs.service may (actually must) run and everything works properly but, doing so, I don't have the advantage of one central configuration location any more. The preferred scenario for each server would be to mount its local shares via fstab and the remote shares via sssd automount. Am I missing something?
Thanks in advance, Petros
-- Dr. TRIANTAFYLLIDIS PETROS E-MAIL: trian@auth.gr ^^^^^^^^^^^^^^^^^^^^^^^^^^ http://users.auth.gr/trian Aristotle University - Department of Geophysics, POBox 111, 54124 Thessaloniki-GREECE - TEL:+30-2310998585 <+30%20231%20099%208585>, FAX:2310991403
Prasun Gera via FreeIPA-users freeipa-users@lists.fedorahosted.org writes:
The only thing I would be interested in knowing is if there is a performance penalty to mounting NFS locally. Ideally, it should be smart enough to know that, but I'm not sure if it is.
On my NFS server /home is a local ext4 mount and exportet. The clients automount it as /zentral. autofs.zentral contains:
* -fstype=nfs4,rw,sec=krb5p,soft,rsize=8192,wsize=8192 nfs.example.org:/home/&
When I access /zentral/jochen I get the following mount:
/dev/mapper/home_lv on /zentral/jochen type ext4 (rw,noatime,errors=remount-ro,data=ordered)
That seems to be a bind mount.
Jochen
freeipa-users@lists.fedorahosted.org
-
Jochen Hein -
Petros Triantafyllidis -
Prasun Gera