On 7 May 2008, at 9:50 am, Fredrik Olofsson wrote:
On Wednesday, May 07, 2008 at 09:10:58 +0100, Tim Cutts wrote:
This is a well known upstream bug, and affects kernels from 2.6.24
onward. I believe there is a workaround - use autofs as the default
mount type, so in your /etc/am-utils/amd.conf [global] section, you
need:
mount_type = autofs
Obviously, for this to work you need autofs support in your kernel.
Please can you try this for me and tell me if you have any success?
Adding "mount_type = autofs" fixes the problem for my other maps (not
for the /net map, and I still get the same log output for the /net
map).
I don't need the /net map, so this workaround is ok with me.
A little strange it worked with 2.6.24 before..
Actually, it didn't work properly before. There's a problem with am-
util's NFS locking with any version of the kernel from 2.6.19
onwards. It's just that 2.6.25 is the first to start actually
complaining about it, whereas in 2.6.19-2.6.24 the locking just
doesn't work properly. But then, no-one ever trusted file locking
over NFS anyway, right? ;-)
The upstream authors have been distressingly quiet about the whole
thing. I'll look into seeing if I can get the /net map to work, but I
suspect it may depend on the NFS functionality.
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]
