Re: [Samba] Samba locking problem - is this a bug ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 25 Feb 2003, System Administrators At Netclime Inc. wrote: What you mean, by the program opening the file decides how to open it ? Is it depend on the filesystem handling of open calls ? I mean - it doesn't matter ith which program I create the file on the share (I tried 3-4 vaious) this DENY_FCB RDWR shows always. These are DOS open/deny modes. The client requested them. Samba maps these onto posix locks on the file system, but some of the (e.g. deny modes) don't map at all so smbd has to maintain them internally for clients. My point is, that shouldn't SAMBA server take care of lost connection to the clients and remove the file locks ? Samba does after a reasonable time. We don't immediately know that the client has gone away. Do you think it would be a better solution for Samba to give away locks because someone tripped over a hub and unplugged it for a few seconds? And why share modes = no doesn;t remove support for DENY_FCB and other similar modes ? What version did you say you were running? I haven't look at that option since it got added back in. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+X3RFIR7qMdg1EfYRAhkwAJ9W7yJnhajEHDUikCSRjmHpGI7tIwCcC6ph YiLKCJWrAuPCIyN6zXU9iWQ= =30nj -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba locking problem - is this a bug ?
Hi, I wonder why linux client should request DOS open/deny modes - but OK, I managed to see that as Kurt says, this depend on the program that opens the file. Unfortunately for me the daemon we use creates the file with DENY_FCB. :( You are right - it seems I missed the configuration directive about this check, when samba should release the locks. I think Kurt point me to the correct opitons - keep alive and the socket options. Possibly I'll need something like keepalive = 10 or something like this. I haven't had time recently to check this. For the share modes = no - I tried it on 2.2.3a; on 2.2.6 (I think) and I'm not sure (but I'll try it later for sure) on 2.2.7a - these were the sources I had so I just compiled them one after another. Regards Kosta - Original Message - From: Gerald (Jerry) Carter [EMAIL PROTECTED] To: System Administrators At Netclime Inc. [EMAIL PROTECTED] Cc: Kurt Weiss [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Friday, February 28, 2003 16:37 Subject: Re: [Samba] Samba locking problem - is this a bug ? -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 25 Feb 2003, System Administrators At Netclime Inc. wrote: What you mean, by the program opening the file decides how to open it ? Is it depend on the filesystem handling of open calls ? I mean - it doesn't matter ith which program I create the file on the share (I tried 3-4 vaious) this DENY_FCB RDWR shows always. These are DOS open/deny modes. The client requested them. Samba maps these onto posix locks on the file system, but some of the (e.g. deny modes) don't map at all so smbd has to maintain them internally for clients. My point is, that shouldn't SAMBA server take care of lost connection to the clients and remove the file locks ? Samba does after a reasonable time. We don't immediately know that the client has gone away. Do you think it would be a better solution for Samba to give away locks because someone tripped over a hub and unplugged it for a few seconds? And why share modes = no doesn;t remove support for DENY_FCB and other similar modes ? What version did you say you were running? I haven't look at that option since it got added back in. cheers, jerry - - Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+X3RFIR7qMdg1EfYRAhkwAJ9W7yJnhajEHDUikCSRjmHpGI7tIwCcC6ph YiLKCJWrAuPCIyN6zXU9iWQ= =30nj -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba locking problem - is this a bug ?
Kostadin Galabov schrieb: Hi, I asked this once and no one seem to answer. So I'm trying once again: I have the following problem: I have a linux samba server and a lot of linux clients that connect to it. What I noticed is that if one of the clients create new file and starts do some operation on it - the file is unreadable for all other clients (output od smbstatus: DENY_FCB RDWR NONE) - which is OK I the type, how a file is opened, is decided by the programm, which is opening. suppose. But if the connection between the client and the server disappears while client is working on the newly created file, the file you mean breaks? stays locked and in some occasions even when the connection is established again the file stays locked, the client cannot access the mounted drive - and the client should be restarted. Which is strange I at this time samba does not know, that the client is death. - seems, that the client hangs. noticed that if a Windows client do the same operation - the file is at least readable for other clients. the other client may have read access to the file. - the broken client has a hangup in communication. I played a lot with the lock options and tried to remove the DENY_FCB - setting share modes = no but nothing helped - I have this problem. So please advice - how can I prevent this file locking when connection between master and client disappears ? For me this look like a bug. that's not really successfull. - my mention is, that your client has a big problem. - samba kills the locking after timeout, if the client is death. - in your case it seems, the client answers to a keep alive, but cannot access the network... - so samba keeps the locking. i cannot really help, without further information. so, if the problem exists again, try something like that first: - ping to the client - check, if u have access from the client to another client - check, if u have access from another client to the broken one - check ifconfig for error packages on server and client. Regards Kostadin Galabov Netclime Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba locking problem - is this a bug ?
What you mean, by the program opening the file decides how to open it ? Is it depend on the filesystem handling of open calls ? I mean - it doesn't matter ith which program I create the file on the share (I tried 3-4 vaious) this DENY_FCB RDWR shows always. After the connection between the client that creates the file and the server breaks - no other client has even read access to the file - the file still has DENY_FCB set. I made this sample test (all three pcs - the server abd PC1 and PC2 are in local LAN): 1. Mount 'share' on PC1 and PC2 (both linuxes) 2. on PC1 used mcedite to open a sample file 1.txt (I tried this with different programs). PC2 cannot access 1.txt. 3. Write something in 1.txt, save it and then unplug the network cable of PC1 4. Now still PC2 cannot access file 1.txt - it still has DENY_FCB. My point is, that shouldn't SAMBA server take care of lost connection to the clients and remove the file locks ? And why share modes = no doesn;t remove support for DENY_FCB and other similar modes ? regards Kosta - Original Message - From: Kurt Weiss [EMAIL PROTECTED] To: Kostadin Galabov [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 13:38 Subject: Re: [Samba] Samba locking problem - is this a bug ? Kostadin Galabov schrieb: Hi, I asked this once and no one seem to answer. So I'm trying once again: I have the following problem: I have a linux samba server and a lot of linux clients that connect to it. What I noticed is that if one of the clients create new file and starts do some operation on it - the file is unreadable for all other clients (output od smbstatus: DENY_FCB RDWR NONE) - which is OK I the type, how a file is opened, is decided by the programm, which is opening. suppose. But if the connection between the client and the server disappears while client is working on the newly created file, the file you mean breaks? stays locked and in some occasions even when the connection is established again the file stays locked, the client cannot access the mounted drive - and the client should be restarted. Which is strange I at this time samba does not know, that the client is death. - seems, that the client hangs. noticed that if a Windows client do the same operation - the file is at least readable for other clients. the other client may have read access to the file. - the broken client has a hangup in communication. I played a lot with the lock options and tried to remove the DENY_FCB - setting share modes = no but nothing helped - I have this problem. So please advice - how can I prevent this file locking when connection between master and client disappears ? For me this look like a bug. that's not really successfull. - my mention is, that your client has a big problem. - samba kills the locking after timeout, if the client is death. - in your case it seems, the client answers to a keep alive, but cannot access the network... - so samba keeps the locking. i cannot really help, without further information. so, if the problem exists again, try something like that first: - ping to the client - check, if u have access from the client to another client - check, if u have access from another client to the broken one - check ifconfig for error packages on server and client. Regards Kostadin Galabov Netclime Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
