Re: fcntl: No locks available (errno = 37)
On Tue, 16 Nov 1999, Dan Lipofsky wrote: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) If the file does not exist it successfully creates it but leaves it length zero. If I try to save to a file on the local file system it works fine. Can anyone help me out here? I don't know which Kernels comes with RedHat 6.1, but I presume it's 2.2.*. If your NFS server supports locking (Linux userspace nfsd doesn't, the knfsd does, if it is compiled with the correct options), everything should be okay, but you shouldn't miss to start lockd and statd on both machines. If your NFS server doesn't support locking, you have to add the option "nolock" to the mount options for this filesystem on the client machine (otherwise Linux 2.2.* on the client will complain). In addition to this you should upgrade to at least kernel 2.2.13, because otherwise you will loose mail (there is a feature in 2.2.* kernels which flushes the cache of a file when it is locked, but in kernel =2.2.12 this feature did only work if the server supports locking. Since 2.2.13 this also works for servers which do not support locking). Ciao Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ *
Re: fcntl: No locks available (errno = 37)
Hi! On Die, Nov 16, 1999 at 09:05:02 -0200, Lalo Martins wrote Copying to falcon/teste...lockd: failed to monitor 192.168.0.76 fcntl: No available locks (errno = 79) Is knfs compiled with --enable-secure-statd? If yes, disable it. Shade and sweet water! Stephan -- | Stephan SeitzE-Mail: [EMAIL PROTECTED] | | WWW: http://fsing.fs.uni-sb.de/~stse/| | PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html | PGP signature
Re: fcntl: No locks available (errno = 37)
On 1999-11-16 18:09:17 -0600, David DeSimone wrote: If you are *certain* that every mail-handling program at your site uses the same dot-locking mechanism, you can reconfigure Mutt with --disable-fcntl, and then you won't have this problem. But if you're wrong, and there is some program that does try to perform fcntl-locks as the only method to prevent synchronization problems, then the two programs can collide and trash the folder if they access it at the same time. When doing this, make sure you disable caching on the NFS client. -- http://www.guug.de/~roessler/
Re: fcntl: No locks available (errno = 37)
On Tue, Nov 16, 1999 at 03:52:11PM -0600, Dan Lipofsky wrote: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) If the file does not exist it successfully creates it but leaves it length zero. If I try to save to a file on the local file system it works fine. Can anyone help me out here? With the help of every here, I did fix the problem. First I looked on the server, and saw the lockd process was defunct. We restarted that, but it did not help. Latter I thought to look on the client, saw there was no lockd, started it, and that fixed everything. While all this was going on, I noticed that I only get this error message when saving from a normal folder, not when saving from an IMAP folder. It failed in both cases, I just did not get notified when saving from an IMAP folder. I wonder why that is? I was saving to a regular file in both cases. Thanks, - Dan
Re: fcntl: No locks available (errno = 37)
Roland Rosenfeld [EMAIL PROTECTED] wrote on Wed, 17 Nov 1999: So flock(2) may not be the best idea if you want to access your mail via NFS... Apparently. IMHO, any incoming mail folders which are accessed over NFS should be in Maildir format anyway, it's pretty much the only sane choice. As this thread quite clearly shows, file locking and NFS don't really mix. Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy scifi, the Corrs / Practice random acts of kindness and senseless acts of beauty.
Re: fcntl: No locks available (errno = 37)
On Tue, Nov 16, 1999 at 06:09:17PM -0600, David DeSimone wrote: Lalo Martins [EMAIL PROTECTED] wrote: Oh, one more tidbit: I _can_ save attachments. Go figure. That's because attachments are saved to *files*, while messages are saved to *folders*. So attachments don't require any locking (unless you're saving a message/rfc822 type, which is a message, but now it's getting confusing). As a minor side issue: is there a way to save message to a *file* (i.e. without the locking)? Dotlocking does not work on FAT partitions... Best Regards, Marius Gedminas -- UNIX is user friendly. It's just selective about who its friends are.
Re: fcntl: No locks available (errno = 37)
Dan Lipofsky ([EMAIL PROTECTED]) said: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) Is lockd running? What sort of NFS server are you trying to save to? Bill
Re: fcntl: No locks available (errno = 37)
* Dan Lipofsky ([EMAIL PROTECTED]) [991116 21:53]: I am using mutt-1.0pre3us on Red Hat 6.1 Linux. When ever I try to save a message to a file on a network file system I get fcntl: No locks available (errno = 37) If the file does not exist it successfully creates it but leaves it length zero. If I try to save to a file on the local file system it works fine. Can anyone help me out here? - Dan I think the problem here lies with fcntl somehow wanting to make use of a lock daemon on the nfs file server. Someone correct me if wrong. Note that NFS lock daemons have a history of sucking, on pretty much all platforms. Userspace Linux NFS servers simply have _no_ lock daemon. The kernel nfs daemon has a lock daemon, if you run it, though I'm not sure it's perfect. As a result, I pretty much always build mutt with --disable-fcntl --enable-flock on linux. I don't know what I'm missing, but at least it works. -josh -- SuSE Inc. Tel: +1-510-628-3380 580 2nd Street, #210Fax: +1-510-628-3381 Oakland, CA 94607 Email: [EMAIL PROTECTED] USA WWW: http://www.suse.com
Re: fcntl: No locks available (errno = 37)
On Tue, Nov 16, 1999 at 08:07:30PM -0200, Lalo Martins wrote: ditto Ok, ``me too''s suck :-) more info: Copying to falcon/teste...lockd: failed to monitor 192.168.0.76 fcntl: No available locks (errno = 79) So it is a lockd issue. I don't run a lockd. (Debian, mutt 1.0pre3-1.2 - newer ones didn't compile on the sparc port, it seems, but the version in the PCs gives the same error) []s, |alo + -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:[EMAIL PROTECTED] pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar
Re: fcntl: No locks available (errno = 37)
Oh, one more tidbit: I _can_ save attachments. Go figure. []s, |alo + -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:[EMAIL PROTECTED] pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness -- http://zope.gf.com.br/BroDar
Re: fcntl: No locks available (errno = 37)
Lalo Martins [EMAIL PROTECTED] wrote: Oh, one more tidbit: I _can_ save attachments. Go figure. That's because attachments are saved to *files*, while messages are saved to *folders*. So attachments don't require any locking (unless you're saving a message/rfc822 type, which is a message, but now it's getting confusing). Basically, Mutt wants to fcntl-lock the folder, to be safe against someone else writing to it. Your NFS client is not running the necessary daemon to coordinate that lock with the server, so it fails, and Mutt gives up rather than possibly trash your mailbox. If you are *certain* that every mail-handling program at your site uses the same dot-locking mechanism, you can reconfigure Mutt with --disable-fcntl, and then you won't have this problem. But if you're wrong, and there is some program that does try to perform fcntl-locks as the only method to prevent synchronization problems, then the two programs can collide and trash the folder if they access it at the same time. Best is to fix the locking problem, as you may have other programs that want to lock files, too. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
