Bug#682810: [Pkg-samba-maint] Bug#682810: samba: Strange message probabilly generating file access errors
If you get corruption when you disable locking, there must still be some access from one client while the other one is using the file. Now i have this and the problem is worse: When the connection is closed, when the process with the PID ends at server, the file is removed!!! The system locks the file, if I wait some time, the locked file is simple removed fro server! oplocks = False level2 oplocks = False locking = no strict locking = no blocking locks = no Could you describe the exact steps needed to reproduce the problem when locking is enabled? What application are you using? How long after the first client closes the file did you try to access it on the second client? Does it work if the first client disconnects? Or if the first client machine is shut down? I'm not certainly about how happens... the frequency is with .PSD photoshop files, but can occurs with other files sporadically, but it's difficult predict. While using Adobe Photoshop, if at least 2 people opens the same file, the file still locked, and remains inacessible and, now, is removed after the first time the locked message occurs. At Adobe Photoshop, I see the message I have no permission to access the file. After this, when the file is removed after the process ends at server, It's possible save again. If I forget save the file, it's lost. I think this happens more frequently as larger are the files. I don't know how to measure the time, but I'm certainly if the second opens when the first is opened (and this can be seconds of difference), the bug happens. But happened in times I don't understood yet. If the first client disconnects, the file still locked forever. To don't lost the file, I can copy at server with another name, for example... The same happens if the first machine is shut down... What is the output of smbclient when the problem occurs? (please check to see that this output does not contain sensitive information before sending it to the bug report) I've tryed smbstatus and do not saw nothing different The fact that you can get access when you disable locking indicates that you don't have a permission issue, but a locking issue. This problem is probably not a debian specific issue. I suspect it is a configuration issue. It might be better to try via the samba mailing list or IRC channel: I will try both. But, anyway, I think this is a critical problem, files are removed or corrupted... And I don't know how proceed with this anymore... Saulo
Bug#682810: [Pkg-samba-maint] Bug#682810: samba: Strange message probabilly generating file access errors
Updating: Samba 3.6.7 at experimental do not solves this problem. And I think none of the bugs solved at 3.6.8 are this too. 2012/9/17 Saulo Soares de Toledo saulotol...@gmail.com If you get corruption when you disable locking, there must still be some access from one client while the other one is using the file. Now i have this and the problem is worse: When the connection is closed, when the process with the PID ends at server, the file is removed!!! The system locks the file, if I wait some time, the locked file is simple removed fro server! oplocks = False level2 oplocks = False locking = no strict locking = no blocking locks = no Could you describe the exact steps needed to reproduce the problem when locking is enabled? What application are you using? How long after the first client closes the file did you try to access it on the second client? Does it work if the first client disconnects? Or if the first client machine is shut down? I'm not certainly about how happens... the frequency is with .PSD photoshop files, but can occurs with other files sporadically, but it's difficult predict. While using Adobe Photoshop, if at least 2 people opens the same file, the file still locked, and remains inacessible and, now, is removed after the first time the locked message occurs. At Adobe Photoshop, I see the message I have no permission to access the file. After this, when the file is removed after the process ends at server, It's possible save again. If I forget save the file, it's lost. I think this happens more frequently as larger are the files. I don't know how to measure the time, but I'm certainly if the second opens when the first is opened (and this can be seconds of difference), the bug happens. But happened in times I don't understood yet. If the first client disconnects, the file still locked forever. To don't lost the file, I can copy at server with another name, for example... The same happens if the first machine is shut down... What is the output of smbclient when the problem occurs? (please check to see that this output does not contain sensitive information before sending it to the bug report) I've tryed smbstatus and do not saw nothing different The fact that you can get access when you disable locking indicates that you don't have a permission issue, but a locking issue. This problem is probably not a debian specific issue. I suspect it is a configuration issue. It might be better to try via the samba mailing list or IRC channel: I will try both. But, anyway, I think this is a critical problem, files are removed or corrupted... And I don't know how proceed with this anymore... Saulo
Bug#682810: [Pkg-samba-maint] Bug#682810: Bug#682810: samba: Strange message probabilly generating file access errors
Soalo, On Fri, Jul 27, 2012 at 03:17:28PM -0300, Saulo Soares de Toledo wrote: 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 ) Did you try with oplocks enabled? The manual only says oplock and force user can lead to performance degradation when the network is unreliable. It doesn't say they should never be used together. 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. If you get corruption when you disable locking, there must still be some access from one client while the other one is using the file. Could you describe the exact steps needed to reproduce the problem when locking is enabled? What application are you using? How long after the first client closes the file did you try to access it on the second client? Does it work if the first client disconnects? Or if the first client machine is shut down? What is the output of smbclient when the problem occurs? (please check to see that this output does not contain sensitive information before sending it to the bug report) The fact that you can get access when you disable locking indicates that you don't have a permission issue, but a locking issue. This problem is probably not a debian specific issue. I suspect it is a configuration issue. It might be better to try via the samba mailing list or IRC channel: https://lists.samba.org/mailman/listinfo/samba http://www.samba.org/samba/irc.html 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? I suspect the quota error you are seeing in the log is not related to the locking problem. If you suspect otherwise, you could try to rebuild the samba server without quota support. Cheers, Ivo De Decker -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682810: [Pkg-samba-maint] Bug#682810: samba: Strange message probabilly generating file access errors
Quoting Saulo Soares de Toledo (saulotol...@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 ext3defaults0 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?
Bug#682810: [Pkg-samba-maint] Bug#682810: Bug#682810: samba: Strange message probabilly generating file access errors
Also, can you include your smb.conf file and information about the clients you are using (OS, version, ...). I have posted a link to my smb.conf above now. And other important informations too. My clients are: - MS Windows 7 (where the problems occurs with frequency) - MS Windows XP - 1 Linux machine (mine) Are you using Mac OS X with unix extentions? Is so, your problem might be similar to this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532856 In that case, you can resolve the problem by setting 'unix extensions = no' No Mac OS X here, but I tested anyway. The only thing who happened here was my Linux Machine can't access the shares mounted at fstab. The problem at Windows 7 machines persists. Thanks Saulo
Bug#682810: [Pkg-samba-maint] Bug#682810: Bug#682810: samba: Strange message probabilly generating file access errors
Hi, On Wed, Jul 25, 2012 at 04:46:14PM -0600, Christian PERRIER wrote: 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. Also, can you include your smb.conf file and information about the clients you are using (OS, version, ...). Are you using Mac OS X with unix extentions? Is so, your problem might be similar to this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532856 In that case, you can resolve the problem by setting 'unix extensions = no' Cheers, Ivo -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682810: samba: Strange message probabilly generating file access errors
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 In both cases, there are this error message (even with log and debug level = 5): [2012/07/25 20:42:06.251977, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! [2012/07/25 20:42:06.252185, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! [2012/07/25 20:42:06.253704, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! [2012/07/25 20:42:06.253910, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! I think there are something related, since Samba 3.4 with the same config does not bring us this bug. Some helps at other distribution forums suggest: ../configure with --with-quotas=no. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682810: [Pkg-samba-maint] Bug#682810: samba: Strange message probabilly generating file access errors
tags 682810 moreinfo thanks Quoting Saulo Soares de Toledo (saulotol...@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 In both cases, there are this error message (even with log and debug level = 5): [2012/07/25 20:42:06.251977, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! [2012/07/25 20:42:06.252185, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! [2012/07/25 20:42:06.253704, 0] lib/sysquotas.c:405(sys_get_quota) sys_path_to_bdev() failed for path [.]! [2012/07/25 20:42:06.253910, 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. I think there are something related, since Samba 3.4 with the same config does not bring us this bug. Some helps at other distribution forums suggest: ../configure with --with-quotas=no. This is definitely not an option, I'm afraid. Quota support *is* expected from our users. signature.asc Description: Digital signature
