[Pkg-samba-maint] Bug#682810: Bug#682810: samba: Strange message probabilly generating file access errors

[Saulo Soares de Toledo]

>
> Quoting Saulo Soares de Toledo (saulotoledo at gmail.com):
> > Source: samba
> > Version: 3.6.6
> > Severity: important
> >
> > I'm using Samba 3.6.6 at Debian Wheezy and there are 2 problems
> happening at
> > my shares:
> >
> > 1) Some files can't be removed
> > 2) The error reported at https://bugzilla.samba.org/show_bug.cgi?id=9051
>
> I don't see anythign related to upstream bug #9051


Both appeared at same time, and the logs at level 5 shows the same error
when the problems occurs:
[2012/07/25 20:42:06.251977,  0] lib/sysquotas.c:405(sys_get_quota)
   sys_path_to_bdev() failed for path [.]!


Level 10 log is much better. And we would probably  need much more
> information such as the settings of this share, the underlying
> filesystem, the permissions on files where you have problems, etc.
>

The permissions at the files with ant without problems are the same, where
"arquivos:arquivos" is the user/group forced at samba with "force user". An
example:

# ls Home_alterado7.psd  -l
-rwxrw---- 1 arquivos arquivos 92238357 Jul 26 09:05 Home_alterado7.psd

There is no special attributes at files:
# lsattr Home_alterado7.psd
---------------- Home_alterado7.psd

And I have no ACL support in my ext3 system. At /etc/fstab:
/dev/md1        /home           ext3    defaults        0       2

Then, there are some error while Samba try control the lockings.

The smb.conf is the same attached at bugzilla:
https://bugzilla.samba.org/attachment.cgi?id=7710

Aditionally, I have tested at shares:

        oplocks = False
        level2 oplocks = False
#       share modes = no
#       locking = no
        strict locking = no
        blocking locks = no

Samba manual told us force user + oplocks enabled is a problem, then I have
deactivated it (See "Beware of Force User" at
www.samba.org/samba/docs/man/Samba-HOWTO-Collection/locking.html )
"share modes = no" is deprecated and do not worked while activated. The
lockings are with "no", but the error still...

"locking = no" worked, but some large files are being corrupted, and this
problem is worse than the deny.



> This is definitely not an option, I'm afraid. Quota support *is*
> expected from our users.
>

How we can remove that erros from samba with quota enabled?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-samba-maint/attachments/20120727/633c746f/attachment.html>