Re: With smb1 unix extensions gone, any way to export existing symlinks to Linux clients as symlinks?

"Dr. Thomas Orgis via samba" <[email protected]> Tue, 28 Apr 2026 10:40:53 +0200
Newsgroups gmane.network.samba.general
Organization Universität Hamburg
Message-ID <20260428104053.5b8ab791@plasteblaster>
Am Mon, 27 Apr 2026 16:05:05 +0200
schrieb Ralph Boehme <[email protected]>:

> maybe just too old version of Samba and/or kernel. It works here with 
> Samba master and kernel 6.17. Samba versions starting with 4.24 should 
> be fine. Older kernels had issue.

It's kernel 6.6 and samba 4.17 from Debian 12, as noted later. So yes,
I missed the point that this version is simply too old to do SMB3 with
posix extensions.

> > follow symlinks (S)
> > 
> >      This parameter allows the Samba administrator to stop smbd(8) from
> >      following symbolic links in a particular share. Setting this
> >      parameter to no prevents any file or directory that is a symbolic
> >      link from being followed (the user will get an error). This option
> >      is very useful to stop users from adding a symbolic link to
> >      /etc/passwd in their home directory for instance. However it will
> >      slow filename lookups down slightly.  
> 
> Iirc this is basically ignored when POSIX is negotiated.

That would also be good to have documented.

To wrap up my convoluted earlier mail:

1. My current situation can be handled by switching to smb1 with unix
   extensions. The good (bad) old way. It works and is fast.

2. To avoid annoying error messages for implicit getxattr() calls, I
   also need to add noacl mount option.

3. SMB3 and the presence of a cvmfs FUSE mount in the share cause about
   a second delay on listings. With SMB1, that is down to milliseconds.

I hope point 3 will be resolved with newer samba, otherwise I'll have
to debug that interaction then.

Until SMB3 is working right, I do hope that vers=1.0 for mount.cifs and
NT1 support in samba stays as an option. There are these fringe use
cases like 'quickly fire up a world-readable share with a userspace
process' that just work well with the old code. Maybe switch NT1
protocol support to read-only mode in samba before actually removing it.


Alrighty then,

Thomas

-- 
Dr. Thomas Orgis
HPC @ Universität Hamburg

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba