Public bug reported:
Binary package hint: smbfs
I have mounted Samba-share on a (Ubuntu-) server to a Gutsy desktop:
[EMAIL PROTECTED]:~cat /etc/fstab
//lin01/public /media/lin01-public smbfs
lfs,fmask=0777,dmask=0777,codepage=cp850,iocharset=utf8 0 0
That works OK:
[EMAIL PROTECTED]:~$ mount
//lin01/public on /media/lin01-public type smbfs (rw)
But when I try to access a folder which is actually a symlink on the (server)
share it self, it refuses, giving the following error:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ cd mp3
bash: cd: mp3: No such file or directory
This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normally only visible on the server it self):
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 1
lrwxrwxrwx 1 root root 22 2007-04-09 11:22 mp3 -> /data/public/music/mp3
lrwxrwxrwx 1 root root 28 2006-10-20 22:17 mp3-extra ->
/data/public/music/mp3-extra
(watch 'l' for link)
When I do this in Feisty, it is as expected:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 8
drwxrwxrwx 1 root root 4096 2007-06-03 23:55 mp3
drwxrwxrwx 1 root root 4096 2007-04-09 17:57 mp3-extra
(watch 'd' for directory)
My problem is two folded:
- is it normal I can see the symlink info (different behaviour in Feisty)
- why are symlink folders on a samba-share not accessible?
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Binary package hint: smbfs
- I have mounted Samba-share on a (Ubuntu-) server to a Gutsy desktop:
+ I have mounted a Samba-share on a (Ubuntu-) server to a Gutsy desktop:
[EMAIL PROTECTED]:~cat /etc/fstab
//lin01/public /media/lin01-public smbfs
lfs,fmask=0777,dmask=0777,codepage=cp850,iocharset=utf8 0 0
- That works OK:
+ That works OK for most of the folders and files I am accessing:
[EMAIL PROTECTED]:~$ mount
- ....
//lin01/public on /media/lin01-public type smbfs (rw)
But when I try to access a folder which is actually a symlink on the (server)
share it self, it refuses, giving the following error:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ cd mp3
bash: cd: mp3: No such file or directory
- This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normaaly only visible on the server it self):
- [EMAIL PROTECTED]:~$ cd /media/lin01-public/music/all/
+ This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normally only visible on the server it self):
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 1
lrwxrwxrwx 1 root root 22 2007-04-09 11:22 mp3 -> /data/public/music/mp3
lrwxrwxrwx 1 root root 28 2006-10-20 22:17 mp3-extra ->
/data/public/music/mp3-extra
+ - see 'l' = link as found objects
- When I do this in Feisty, it is as expected:
+ When I do this in Feisty, it works as expected:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 8
drwxrwxrwx 1 root root 4096 2007-06-03 23:55 mp3
drwxrwxrwx 1 root root 4096 2007-04-09 17:57 mp3-extra
+ - see 'd' = directory as found objects
My problem is two folded:
- is it normal I can see the symlink info (different behaviour in Feisty)
- why are symlink folders on a samba-share not accessible?
** Description changed:
Binary package hint: smbfs
- I have mounted a Samba-share on a (Ubuntu-) server to a Gutsy desktop:
+ I have mounted Samba-share on a (Ubuntu-) server to a Gutsy desktop:
[EMAIL PROTECTED]:~cat /etc/fstab
//lin01/public /media/lin01-public smbfs
lfs,fmask=0777,dmask=0777,codepage=cp850,iocharset=utf8 0 0
- That works OK for most of the folders and files I am accessing:
+ That works OK:
[EMAIL PROTECTED]:~$ mount
+ ....
//lin01/public on /media/lin01-public type smbfs (rw)
But when I try to access a folder which is actually a symlink on the (server)
share it self, it refuses, giving the following error:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ cd mp3
bash: cd: mp3: No such file or directory
- This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normally only visible on the server it self):
+ This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normaaly only visible on the server it self):
+ [EMAIL PROTECTED]:~$ cd /media/lin01-public/music/all/
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 1
lrwxrwxrwx 1 root root 22 2007-04-09 11:22 mp3 -> /data/public/music/mp3
lrwxrwxrwx 1 root root 28 2006-10-20 22:17 mp3-extra ->
/data/public/music/mp3-extra
- - see 'l' = link as found objects
- When I do this in Feisty, it works as expected:
+ When I do this in Feisty, it is as expected:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 8
drwxrwxrwx 1 root root 4096 2007-06-03 23:55 mp3
drwxrwxrwx 1 root root 4096 2007-04-09 17:57 mp3-extra
- - see 'd' = directory as found objects
My problem is two folded:
- - is it normal I can see the symlink info (different behaviour in Feisty)
+ - is it normal I can see the symlink info client side though samba (different
behaviour in Feisty)?
- why are symlink folders on a samba-share not accessible?
** Description changed:
Binary package hint: smbfs
I have mounted Samba-share on a (Ubuntu-) server to a Gutsy desktop:
[EMAIL PROTECTED]:~cat /etc/fstab
//lin01/public /media/lin01-public smbfs
lfs,fmask=0777,dmask=0777,codepage=cp850,iocharset=utf8 0 0
That works OK:
[EMAIL PROTECTED]:~$ mount
- ....
//lin01/public on /media/lin01-public type smbfs (rw)
But when I try to access a folder which is actually a symlink on the (server)
share it self, it refuses, giving the following error:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ cd mp3
bash: cd: mp3: No such file or directory
- This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normaaly only visible on the server it self):
- [EMAIL PROTECTED]:~$ cd /media/lin01-public/music/all/
+ This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normally only visible on the server it self):
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 1
lrwxrwxrwx 1 root root 22 2007-04-09 11:22 mp3 -> /data/public/music/mp3
lrwxrwxrwx 1 root root 28 2006-10-20 22:17 mp3-extra ->
/data/public/music/mp3-extra
When I do this in Feisty, it is as expected:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 8
drwxrwxrwx 1 root root 4096 2007-06-03 23:55 mp3
drwxrwxrwx 1 root root 4096 2007-04-09 17:57 mp3-extra
My problem is two folded:
- - is it normal I can see the symlink info client side though samba (different
behaviour in Feisty)?
+ - is it normal I can see the symlink info (different behaviour in Feisty)
- why are symlink folders on a samba-share not accessible?
** Description changed:
Binary package hint: smbfs
I have mounted Samba-share on a (Ubuntu-) server to a Gutsy desktop:
[EMAIL PROTECTED]:~cat /etc/fstab
//lin01/public /media/lin01-public smbfs
lfs,fmask=0777,dmask=0777,codepage=cp850,iocharset=utf8 0 0
That works OK:
[EMAIL PROTECTED]:~$ mount
//lin01/public on /media/lin01-public type smbfs (rw)
But when I try to access a folder which is actually a symlink on the (server)
share it self, it refuses, giving the following error:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ cd mp3
bash: cd: mp3: No such file or directory
This is very odd, because I was under the impression that symlinks on
samba-shares are fully transparent (i.e. invisible) from the client side
perspective, but actually, the client gives the the exact symlink info
(something normally only visible on the server it self):
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 1
lrwxrwxrwx 1 root root 22 2007-04-09 11:22 mp3 -> /data/public/music/mp3
lrwxrwxrwx 1 root root 28 2006-10-20 22:17 mp3-extra ->
/data/public/music/mp3-extra
+ (watch 'l' for link)
When I do this in Feisty, it is as expected:
[EMAIL PROTECTED]:/media/lin01-public/music/all$ ls -l
total 8
drwxrwxrwx 1 root root 4096 2007-06-03 23:55 mp3
drwxrwxrwx 1 root root 4096 2007-04-09 17:57 mp3-extra
+ (watch 'd' for directory)
My problem is two folded:
- is it normal I can see the symlink info (different behaviour in Feisty)
- why are symlink folders on a samba-share not accessible?
--
Mount with smbfs treats symlinks invalid
https://bugs.launchpad.net/bugs/134716
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
