On 10 Jun 2008, at 9:27 pm, Philippe Troin wrote:
This is caused by amd's top-level mounts which are mounted by default
with NLM locks enabled (lock mount option). Locks are not required
for the top-level mounts.
The attached patch passes "nolock" to
top-level mount requests.
It's a more fundamental problem than that, I think, Philippe, isn't
it? Have you seen the discussions on the mailing list? Your patch
might be a useful workaround though, until upstream fix the problem
properly. An alternative workaround is to make using autofs for the
intercepts the default configuration. But that isn't entirely
backward compatible with previous behaviour.
The attached patch fixes the problem.
Does it actually fix the problem, or just make the error go away?
What happens if you try to lock files on filesystems that have been
automounted? Does that still work?
Phil.
<am-utils-6.1.5-nolock-toplvl.patch>
Thanks for the patch - glad you're still keeping tabs on am-utils. :-)
Tim
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
