On Mon, Sep 29, 2008 at 08:18:10PM -0400, Just Marc wrote: > Hi, > > > It's basically just a userspace NFS server, right? > > Correct. > > > Could you work around the problem by mounting with -onolock? > > That doesn't seem to help. > > >You might try running wireshark on the "lo" interface and seeing > whether there's any NLM traffic from lockd. > > You guessed right. There's a 12 megabytes per second of NLM traffic on lo. > > unlock call requests and unlock replies saying permission denied, looks > like it just repeats forever in a tight loop. Permission denied on an unlock sounds pretty weird--probably a bug on the server (CFS) side. The client might be able to handle it gracefully, but that's probably not a high priority. So -onlock is the way to go; see Trond's suggestions. Locking will still work, CFS just won't be told about it. That would only be a problem if you had multiple NFS clients doing locking on the same CFS filesystem, but you're only loopback-mounting, so only one client is involved. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
