Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #176540
| From | Reco <recoverym4n@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: autofs config |
| Date | 2017-01-10 10:40 +0100 |
| Message-ID | <sY14m-80P-27@gated-at.bofh.it> (permalink) |
| References | <sXr0R-240-1@gated-at.bofh.it> <sXrkd-2cp-3@gated-at.bofh.it> <sXI1I-4H4-29@gated-at.bofh.it> <sXNkJ-7O3-1@gated-at.bofh.it> <sXRRn-26v-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi. On Mon, Jan 09, 2017 at 06:48:43PM -0500, Harry Putnam wrote: > Reco Wrote: > > Which brings me to this: > > > > 1) What security option are you using (i.e. none, sys, krb5, etc)? > > If unsure, please mount a share by hand and obtain mount options > > from /proc/mounts. > > It appears to be sys (sec=sys) > > 192.168.1.42:/projects/dv /projects/dv nfs4 rw,relatime,vers=4.0,\ > rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,\ > timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.29,local_lock=none,\ > ^^^^^^^ > addr=192.168.1.42 0 0 Ok, that simplifies things somewhat. So it's tcp-over-ipv4 type of NFS4 without any security worth mentioning. > > 3) Stop autofs, start it like this: > > > > /usr/sbin/automount -fd > > > > Mount a filesystem. Watch the debug output. Terminate it with Ctrl+C. > > (below I marked with *** what might be a clue) You missed it by two lines ☺: > get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 6 version 0x30 > get_nfs_info: called with host 191.168.1.42(191.168.1.42) proto 17 version 0x30 > > *** mount(nfs): no hosts available To workaround #828217 please comment out the line with '-host' in /etc/auto.master. > As I mentioned in the OP: > The host involved is a solaris x86 host. The file systems set for > nfs availability are not put into an /etc/exports type setup. That's what they want you to beleive. Please check out /etc/dfs/sharetab on NFS server. > The way it is done on solaris with the zfs file system... is during > the creation of a file system with `zfs create' One of the ways of doing it, certainly not the most easiest one. share(1M) is decade older at least and thousand times easier to use. > So maybe that has something to do with the problem... Hardly. The way you're doing on Solaris it you provide NFS shares to everyone and their dog in read-write mode with sec=sys by NFS versions ranging from two to four. At least these are defaults starting with Solaris 10. The thing that's broken here is autofs, not NFS implementation. Reco
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
autofs config Harry Putnam <reader@newsguy.com> - 2017-01-08 20:10 +0100
Re: autofs config Reco <recoverym4n@gmail.com> - 2017-01-08 20:30 +0100
Re: autofs config Sven Hartge <sven@svenhartge.de> - 2017-01-08 21:30 +0100
Re: autofs config Harry Putnam <reader@newsguy.com> - 2017-01-09 14:20 +0100
Re: autofs config Reco <recoverym4n@gmail.com> - 2017-01-09 20:00 +0100
Re: autofs config Harry Putnam <reader@newsguy.com> - 2017-01-10 00:50 +0100
Re: autofs config Reco <recoverym4n@gmail.com> - 2017-01-10 10:40 +0100
Re: autofs config Harry Putnam <reader@newsguy.com> - 2017-01-10 16:20 +0100
Re: autofs config Reco <recoverym4n@gmail.com> - 2017-01-10 16:40 +0100
Re: autofs config Harry Putnam <reader@newsguy.com> - 2017-01-10 19:00 +0100
Re: autofs config Reco <recoverym4n@gmail.com> - 2017-01-10 19:40 +0100
Re: autofs config Harry Putnam <reader@newsguy.com> - 2017-01-11 01:40 +0100
Re: autofs config [SOLVED] Reco <recoverym4n@gmail.com> - 2017-01-11 07:50 +0100
csiph-web