[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: problem setting user and group on mounting a cifs share - Please help

On Monday 28 April 2008, NN_il_Confusionario wrote:
> On Mon, Apr 28, 2008 at 09:05:37PM +0200, Chris wrote:
> > The server is a Buffalo Link-Stateion (Firmware 1.06).  I don't think
> > it has logging that is normally accesible.
> from what I understand by reading
>  Linkname: Buffalo network-attached storage series - Wikipedia, the free
> encyclopedia URL:
> http://en.wikipedia.org/wiki/Buffalo_network-attached_storage_series
> it is Linux based, so it should have a syslog, so it is quite possible
> that its syslog can be configured for remote logging (in combination
> with a configuration of your local syslog on debian to accept logs from
> that server)
> However, that link also says that the device supports NFS, so I would
> use NFS insted of cifs
> If you still want to use cifs,
>    Linkname: mount.cifs(8) - Linux man page
>         URL: http://linux.die.net/man/8/mount.cifs
> says (with an example) that there is a --verbose option; this might be
> useful to obtain debug information.
> > but why does the same /etc/fstab entry
> >
> > //  /mnt/candj      cifs   
> > user,noauto,credentials=/etc/cred,uid=1000,gid=1000     0       0
> >
> > give completely different results on different machines?
> quite probably there is a difference between the two machines (something
> in /etc/ ? the cifs kernel module ? some other package ? the way that
> the "server" treats the two machines and their users ?)
> In any case this is the reason I asked for debugging info in the logs.
> >  Especially when I explicitly give the uid and gid, these seem to be
> > is ignored when mounting.
> the man page I cited above explains that uid "is ignored when the
> target server supports the CIFS Unix extensions." (the same for gid)

The mount problem does in fact have to do with CIFS Linux Extensions.  See my 
respone to Mark Clarkson in this thread.  I also googled aroung alot to try 
to find out what the rsync errors were but didn't get to far.

Thanks anyway for your extensive suggestions!


C. Hurschler

Reply to: