[linux-cifs-client] CIFS issues with KDE

Bjoern Tore Sund bjorn.sund at it.uib.no
Thu Aug 30 14:29:04 GMT 2007


Jan Engelhardt wrote:
> Hi Wilhelm
> 
> 
> On Aug 30 2007 09:06, Wilhelm Meier wrote:
>> to issue 2: use the serverino-option of mount.cifs
> 
> Yes, thank you - that helped!
> 
>> (perhaps solves also issue 3)
> 
> No it does not. But I found out:
> 
> 	15:29 server:/home/jengelh3/.kde # l
> 	total 8
> 	drwx------  2 jengelh3 users   59 Aug 30 15:29 .
> 	drwx--x--x 13 jengelh3 users 4096 Aug 30 15:29 ..
> 	lrwxrwxrwx  1 jengelh3 users   20 Aug 30 15:27 cache-linux -> /var/tmp/kdecache-jengelh3
> 	lrwxrwxrwx  1 jengelh3 users   15 Aug 30 15:27 socket-linux -> /tmp/ksocket-jengelh3
> 	lrwxrwxrwx  1 jengelh3 users   11 Aug 30 15:27 tmp-linux -> /tmp/kde-jengelh3
> 	lrwxrwxrwx  1 root     root     3 Aug 30 15:29 bar -> foo
> 
> None of these symlinks (all pointing to non-existing files) do NOT appear
> on the client, hence rmdir fails.
> 
> Interestingly, the following...
> 
> 	15:39 server:/home/jengelh3/.kde # l
> 	total 8
> 	drwx------  2 cf   users   89 Aug 30 15:39 .
> 	drwx--x--x 13 cf   users 4096 Aug 30 15:29 ..
> 	lrwxrwxrwx  1 root root     3 Aug 30 15:38 bar -> foo
> 	lrwxrwxrwx  1 root root     3 Aug 30 15:39 baz -> bar
> 	-rw-r--r--  1 root root     0 Aug 30 15:39 foo
> 
> outputs this on the client:
> 
> 	14:40 linux:~ > l .kde
> 	/bin/ls: cannot read symbolic link .kde/bar: Permission denied
> 	/bin/ls: cannot read symbolic link .kde/baz: Permission denied
> 	total 0
> 	drwx------  2 jengelh3 users 0 Aug 30  2007 .
> 	drwx--x--x 13 jengelh3 users 0 Aug 30  2007 ..
> 	lrwxrwxrwx  1 jengelh3 users 3 Aug 30  2007 bar
> 	lrwxrwxrwx  1 jengelh3 users 3 Aug 30  2007 baz
> 	-rw-r--r--  1 jengelh3 users 0 Aug 30  2007 foo
> 
> So I suppose symlinks are fed up somehow. (And relates to setfacl giving -EIO..)

Interesting.  I use cifs for linux file system extensively - on about 
500 client machines.  Here are my setting on the Samba server to get the 
file system to work as Unixish as possible:

         enhanced browsing = yes
         unix extensions = yes
         kernel oplocks = yes
         posix locking = yes
         strict locking = no
         locking = yes
         wide links = yes
         mangled names = no
         delete readonly = No

With unix extensions enabled and the same username on server as on 
client the only option I give to mount.cifs is serverino, and I don't 
have the issue you report.  The "mangled names" one is important.  It 
can screw things up for Windows clients, but is really essential to have 
Samba as a home directory server for Linux clients, or you can't have 
':' in filenames and a lot of stuff gets broken.

-BT
-- 
Bjørn Tore Sund       Phone: 555-84894   Email:   bjorn.sund at it.uib.no
IT department         VIP:   81724       Support: http://bs.uib.no
Univ. of Bergen

When in fear and when in doubt, run in circles, scream and shout.


More information about the linux-cifs-client mailing list