CIFS client bug
eric.h.jarman at gmail.com
Wed Oct 15 14:30:15 UTC 2008
The permissions on the NAS device come out correct when using the SMBFS
module, as well as when connecting from a windows client.
The "noperm" option is supposed to have the server handle all permissions,
the same as what I believe happens when using the SMBFS module. Server
permissions are inherited correctly by files (the Object Inheritance flag in
NTFS), but not by directories (Container Inheritance flag).
On Tue, Oct 14, 2008 at 6:59 PM, Brian McKee <brian.mckee at gmail.com> wrote:
> On Thu, Oct 9, 2008 at 3:58 PM, Eric Jarman <eric.h.jarman at gmail.com>
> > I have found a bug with the CIFS client.
> > Whenever I create a directory under a CIFS mountpoint, the Container
> > Inheritance on the underlying server filesystem is ignored.
> > The CIFS server is a commercial NAS device, pretending to be windows2000
> > with NTFS.
> > The share is mounted with the following options:
> > file_mode=0777,dir_mode=0777,uid=client,gid=client,noperm,nosetuids
> > Dist Version: Ubuntu Server 8.04.1 LTS
> > Kernel: (linux-image-2.6.24-19-server) 2.6.24-19.41
> > Samba: (samba,samba-common) 3.0.28a-1ubuntu4.5
> So why do you think it's the clients fault and not the server? After
> all, why would the client know anything about the server filesystem?
> If it's a commercial NAS device, I'd suggest starting with the vendor,
> unless I'm missing something...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ubuntu-users