Re: [Samba] File locks not always released (Samba 2.2.8)
Hi Rasjid,Jeremy, We have the same problem as Rasjid said, But I'm working with an XFS and ACL's on files and dir (samba 3.0.4). I noticed that when a locked file (for samba) should NOT be locked, there was a problem of wrong autorizations on this file. --x missing or something similar according to what the samba user is autorized to do on this file. putting the good autorizations on, free the lock on this file, and you can do what you want next. look: The problem occured yesterday , I had a file on a share dmc called error.txt the share is root owner and group dmc owner. acl's when the problem occured said : user::r user:root:rwx group:dmc:rwx mask::rwx other::--- ls -l : r--rwx--- error.txt chmoding error.txt to (this is what I wanted before): rwxrwx--- error.txt unlock this file in samba point of view. The problem that I didn't anderstood is that I cannot say why I had : user::r user:root:rwx on file error.txt, cause it must have been : user::rwx user:root:rwx I think it was a copy of group of files from another NOVELL server that made this file r only for user root. I will do some others tests on these days, will keep you informed on this , ok ? Have a nice day Xavier Yes this is a reasonable thing to do. There was an issue in handling the lock database I fixed in 3.0.x recently, this code is similar in 2.2.x so it's possible this is a fixed bug. Your suggestion of a command to manually release a lock is a good one, I'll look at that for later releases. Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- Xavier mailto: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] File locks not always released (Samba 2.2.8)
On Wed, Aug 11, 2004 at 03:18:08PM +1000, Rasjid Wilcox wrote: We have the occasional problem that file locks are not always being released. The result is files that insist on being 'read only' (claiming that the file is already 'in use') or that cannot be deleted or replaced. The problem only happens occasionally, and I have yet to be able to determine a pattern. The problem will usuall resolve itself within 24 hours, but sometimes it is very inconvenient. Firstly, is this a known issue with this version of Samba? If so, does it go away in later versions? Secondly, is there a way to 'manually' release a file lock on the server, for just a specific file? (I'm thinking of a command that could be run on the samba server itself.) Failing that, what about releasing all locks? Google seems to suggest that: Stopping Samba, removing /var/cache/samba/locking.tdb and restarting Samba would do that. Presumably this would be best to do after everyone has logged out of the system? Is this a reasonable thing to do, or is it likely to break something? Yes this is a reasonable thing to do. There was an issue in handling the lock database I fixed in 3.0.x recently, this code is similar in 2.2.x so it's possible this is a fixed bug. Your suggestion of a command to manually release a lock is a good one, I'll look at that for later releases. Thanks, Jeremy. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] File locks not always released (Samba 2.2.8)
We have the occasional problem that file locks are not always being released. The result is files that insist on being 'read only' (claiming that the file is already 'in use') or that cannot be deleted or replaced. The problem only happens occasionally, and I have yet to be able to determine a pattern. The problem will usuall resolve itself within 24 hours, but sometimes it is very inconvenient. Firstly, is this a known issue with this version of Samba? If so, does it go away in later versions? Secondly, is there a way to 'manually' release a file lock on the server, for just a specific file? (I'm thinking of a command that could be run on the samba server itself.) Failing that, what about releasing all locks? Google seems to suggest that: Stopping Samba, removing /var/cache/samba/locking.tdb and restarting Samba would do that. Presumably this would be best to do after everyone has logged out of the system? Is this a reasonable thing to do, or is it likely to break something? We are at the moment stuck with Samba 2.2.8 for support reasons, so upgrading to a newer version of Samba is not an option at the current point in time, although will hopefully become an option within the next 6 months. Thanks, Rasjid. -- Rasjid Wilcox Senior Systems Architect Australian Ethical Investment Ltd Suite 66, Canberra Business Centre Bradfield St, DOWNER ACT 2602 Ph:02 6242 1980 Fax: 02 6242 1987 This email (and any attachments) is confidential and for the persons to whom it is addressed. Any unauthorised reproduction or dissemination of this message is prohibited. Please notify the sender immediately if you have received this message in error. AEI accepts no responsibility for the use of any attachments and/or corrupt files which this email may contain. The contents and opinions expressed by the author of this email are not necessarily those of AEI. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
