search for: enolck

Greetings, We use NFSv4 on our cluster and perform distributed indexing (well, we used to on our previous system which used a simple touch() locking mechanism). I'm having a spot of bother getting Xapian to obtain a lock (hangs on fcntl64()). I've read http://trac.xapian.org/wiki/XapianOverNFS and other list posts, and noted that a lock daemon should be running to allow locks

...in 40.27437 (0 reqs/sec) | Rendering: 2.17903 (5%) | DB: 3.97764 (9%) [http://mail.jerke.be/inscription/new] Processing Base#new (for 84.194.118.193 at Sat Jul 09 16:24:57 UTC 2005) Parameters: {"action"=>"new", "controller"=>"inscription"} Errno::ENOLCK (No locks available - /tmp/ruby_sess.f3af57c120a3fa42): /usr/lib/ruby/1.8/pstore.rb:103:in `flock'' /usr/lib/ruby/1.8/pstore.rb:103:in `transaction'' /usr/lib/ruby/1.8/cgi/session/pstore.rb:90:in `update'' /usr/lib/ruby/1.8/cgi/session/pstore.rb:97:in `close&...

All, I sent a message for help a couple of weeks ago about a samba migration issue. With further testing, we have isolated the issue to Microsoft Outlook (versions 2007 and 2010). All other applications have no issues when they mount the new samba server reading, writing, etc. But, in Outlook, when you try to open an archive (pst file) on the new samba server, it pops up an error "the

Hi there, I have a quite ugly problem with a Samba server. The server is running Linux 2.4.13 and Samba 2.2.2. The NFS-client is running Linux 2.4.5. The windows homedirs are on \\server\username, the UNIX homedirs are NFS mounted by the server. So, whenever I access \\server\username this actually NFS-mounts /nfs/client/home/username. I now have one client machine that causes the following

...0/llvm/include/llvm/Support/system_error.h:540: error: ‘ECHILD’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:544: error: ‘EINVAL’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:546: error: ‘ENOLCK’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:550: error: ‘ENOMSG’ was not declared in this scope /home/carl/Downloads/llvm3.0/llvm/include/llvm/Support/system_error.h:552: error: ‘ENOMSG’ was not declared in this scope /home/carl/Downloads/ll...

...shlwapi: Avoid buffer overflow in PathCombineA. Fran?ois Gouget (8): ole32: Fix StorageImpl_LockRegionSync() to actually wait between locking attempts. ole32: FileLockBytesImpl_WriteAt() should return STG_E_WRITEFAULT for write errors. server: Treat ENOTSUP the same way as ENOLCK, consider locking to be non-functional on that filesystem. ole32: Treat STG_E_LOCKVIOLATION the same way as STG_E_ACCESSDENIED as both indicate locking contention. ole32: Return the correct error in FileLockBytesImpl_*LockRegion*(). msvcrt/tests: Add a trailing '\n' to an...

Hello. I run samba 3.0.21c on RHEL AS 4 EMT_64 U3 and I've experienced a strange problem where smbd will go (and stay) in the D state. While waiting for IO (possibly), these smbd processes do not respond to client requests, thus samba appears to be down. I could not kill these processes via kill -9 , so I rebooted which worked. The only error I could see out of the ordinary would be

...cking issues with HP-UX 11.00 "MCCALL,DON (HP-USA,ex1)" wrote: > > Hi Jeremy, > More info: > With the following program, I DO get an EFBIG error back. > If I change the lock.l_start to a number greater than 2gbyte -1, then no > matter what the offset i choose, I get a ENOLCK instead. > The lseek ALWAYS gives back the EFBIG. > > So what appears to be happening is that there is a 'hierarchy' - if the lock > start (offset) exceeds NFSv2 file limits, then you get ENOLCK, before the > count is checked. If the lock start falls within NFSv2 file limit...

...lts. Reinout On Wednesday 15 August 2001 03:41, MCCALL,DON (HP-USA,ex1) wrote: > Hi Jeremy, > More info: > With the following program, I DO get an EFBIG error back. > If I change the lock.l_start to a number greater than 2gbyte -1, then no > matter what the offset i choose, I get a ENOLCK instead. > The lseek ALWAYS gives back the EFBIG. > > So what appears to be happening is that there is a 'hierarchy' - if the > lock start (offset) exceeds NFSv2 file limits, then you get ENOLCK, before > the count is checked. If the lock start falls within NFSv2 file limits...

...ba-request@lists.samba.org?subject=unsubscribe> List-Archive: http://lists.samba.org/pipermail/samba/ Hi Jeremy, More info: With the following program, I DO get an EFBIG error back. If I change the lock.l_start to a number greater than 2gbyte -1, then no matter what the offset i choose, I get a ENOLCK instead. The lseek ALWAYS gives back the EFBIG. So what appears to be happening is that there is a 'hierarchy' - if the lock start (offset) exceeds NFSv2 file limits, then you get ENOLCK, before the count is checked. If the lock start falls within NFSv2 file limits, you get a EFBIG only i...

...t; "Broken pipe" EDOM (33) => "Math argument out of domain of func" ERANGE (34) => "Math result not representable" closing asm-generic/errno-base.h EDEADLK (35) => "Resource deadlock would occur" ENAMETOOLONG (36) => "File name too long" ENOLCK (37) => "No record locks available" ENOSYS (38) => "Function not implemented" ENOTEMPTY (39) => "Directory not empty" ELOOP (40) => "Too many symbolic links encountered" ENOMSG (42) => "No message of desired type" EIDRM (43) => &qu...

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux