[Samba] l can't "see" files on NFS mounts using 3.6.15, after upgrading from 2.2.8a

[Jordan Verschuer]

Hi Steve,

thanks for jumping in,

I've answered your questions below.


---------- Forwarded message ----------
From: steve <steve at steve-ss.com>
To: samba at lists.samba.org
Cc:
Date: Thu, 12 Dec 2013 10:46:15 +0100
Subject: Re: [Samba] [Sambal can't "see" files on NFS mounts using 3.6.15,
after upgrading from 2.2.8a
On Thu, 2013-12-12 at 01:24 -0800, Linda W wrote:
> On 12/11/2013 10:08 PM, Jordan Verschuer wrote:
> > Thanks Linda, your suggestion is a good one, I think it gives a clue.
> >
> > I created a new samba Share of a NFS mounted folder, i.e. not linked
> > into my original Share, and this shows the same thing, I can't see the
> > files via Win or Mac clients.
> >
> > So this rules out being a wide link issue right?
> >
> > It's now a "sharing an NFS mounted folder via smb" issue right?
> ----
> It would seem so.  Since there are no links involved and you are
> accessing it
> directly, I don't see how links would be at issue.

Hi
How are you re-sharing? Are you re-exporting the nfs mount point itself?

It works if you don't no? IOW,

[stuff]
path = /home/stuff
read only = No

now:
mkdir /home/stuff/nfs
and
mount -t nfs server:/share /home/stuff/nfs

Now you can see the files, yes?


==> I've mounted the NFS like this, and no joy, it still won't let me see
the files.

The only difference is on Solaris 9 the command is mount -F nfs …

Strangely I can copy files in, but once "refreshing" Explorer or Finder
they become hidden.

On 2.2.8a this wasn't a problem.



But:

mount -t nfs server:/share /home/stuff

and you can't?

Other stuff. Are we kerberised? What does the share look like in
smb.conf? What command are you using to mount the nfs share?


==> mount -F nfs… as for Solaris 9.

==> Sorry, i'm not a fully fledged sys admin, how do I check kerberos and
what aspect in particular; simply if it is running or not?

==> smb.conf see below, biograph is the Share that i'd like to mount or
link NFS folders to, which used to work fine linking them in using 2.2.8a.

++++++++++++++++++++++++++++++++++++++++++
# Samba config file created using SWAT
# from UNKNOWN (152.76.10.181)
# Date: 2013/12/12 16:48:45

[global]
  server string = Samba Server
  interfaces = eri0, 152.76.10.3/255.255.255.192
  passdb backend = smbpasswd
  os level = 65
  preferred master = Yes
  domain master = Yes
  wins support = Yes
  remote announce = 152.76.10.255/WORKGROUP
  allow insecure wide links = Yes
  idmap config * : range =
  idmap config * : backend = tdb
  admin users = root, roger, ecat
  printer admin = @ntadmin

[print$]
  path = /usr/local/samba/printers
  admin users = roger, root
  write list = @ntadmin, root
  guest ok = Yes

[biograph]
  comment = biograph
  path = /p3/biograph
  valid users = biograph, roger, steve, stefan, ecat, root, lingfeng, jordan
  admin users =
  read only = No
  wide links = Yes

[roger]
  comment = roger
  path = /home/acacia/roger
  valid users = roger, root
  read only = No

[X2125-A6]
  comment = X2125 A6
  path = /var/spool/samba/print
  printable = Yes
  print ok = Yes

[wenlf]
  comment = lingfeng
  path = /home/karri/lingfeng
  valid users = lingfeng
  admin users =
  read only = No
  browseable = No
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Any other info available?

==> The NFS servers are not NIS+ or LDAP, i.e. no directory service or
mapped user login/authentication service is running, but this wasn't a
problem in 2.2.8a, would something in 3.6.15 have been introduced which
requires these NFS servers to now join or share some user login info?? Or
mapped user or group ID's, etc? Anything along those lines ???


HTH
Steve



Thanks for your help,

it's quite a puzzle!


Cheers,
Jordan