From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Description of problem:
When mounting a samba-share on another computer, using uid and gid
arguments these (uid & gid) gets ignored.
My fstab looks like:
//computer/share /mnt/share smbfs
It works nice in kernel 2.4
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Arjan's kernel 2.6
2. Try to mount a samba-share using some uid&gid
3. Try to write something on the mounted filesystem
Actual Results: The filesystem is mounted read-only, because that the
correct uid & gid wasn't set properly
Expected Results: The mounted filesystem should be mounted with "the
local me" as the owner of the files, as it is with kernel 2.4.x
This is most likely a kernel bug rather than a bug in Samba. I'm
reassigning it to the right folks.
I'm seeing the same problem in FC2 with kernel-2.6.6-1.376, using both
mount -t smbfs and mount.cifs. The shares are mounting, but uid and
gid are not set correctly.
Confirmed this problem on FC2 with kernel-2.6.6-1.453.2.3
seems that the directory of the actual mountpoint gets the right
uid/gid, its just not inherited to the subdirs and files
Confirming bug report and comment #3.
$ cat /etc/fedora-release
Fedora Core release 2 (Tettnang)
$ uname -r
uid/gid are set only the parent directory is right.
This is a major problem since files have uid/gids from a
Solaris box and due to uid/gid colissions smbfs is totaly
- Without UE, smbfs fakes the uid/gid as given to it by smbmnt
and a non-root user can't change it from his own. This is why you can't
set uid/gid with 2.4.
With UE, smbfs ignores the uid/gid and instead accepts the server
the same way nfs or any network fs with unix like id:s would.
Same goes for file modes.
confirmed again, it's like in comment #3 with FC2 kernel 2.6.8-1.521
a patch is floating around in samba bugzilla :
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/