Date: Thu, 13 Jan 2005 18:46:56 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Bruce Campbell <bruce@engmail.uwaterloo.ca> Cc: Paul McKone <pdmckone@engmail.uwaterloo.ca> Subject: Re: flock failure on NFS from 5.3 client to 4.7 server Message-ID: <20050114024656.GA66730@xor.obsecurity.org> In-Reply-To: <1105670575.41e731af8de9a@www.nexusmail.uwaterloo.ca> References: <1105670575.41e731af8de9a@www.nexusmail.uwaterloo.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
On Thu, Jan 13, 2005 at 09:42:55PM -0500, Bruce Campbell wrote:
>
> NFS server: FreeBSD 4.7
> Old Mail server: FreeBSD 4.7, home directories mounted to NFS server
> New Mail server: FreeBSD 5.3, home directories mounted to NFS server
>
> After the mail server upgrade to 5.3, flock gives error "operation not supported"
> on nfs mounted home directories. Example:
>
> Jan 13 00:06:32 mail vacation[92816]: vacation: .vacation: Operation not supported
>
> output from "truss"
>
> open(".vacation.db",0x2,0640) = 3 (0x3)
> fstat(3,0xbfbfd350) = 0 (0x0)
> flock(0x3,0x2) ERR#45 'Operation not supported'
> close(3) = 0 (0x0)
>
> It appears someone else has done substantially more debugging than I:
>
> http://lists.freebsd.org/pipermail/freebsd-questions/2004-September/059777.html
>
> but is seemingly no further ahead.
>
> On our NFS server, rpc.statd is running, but rpc.lockd wasn't. Started
> it, still no worky. Killed it, other 4.7 clients still flock fine.
rpc.lockd needs to be running on *both* client *and* server.
4.x gets away with it because the rpc.lockd implementation does not in
fact implement locking on the client.
Kris
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQFB5zKgWry0BWjoQKURAjCfAJ4nIlRhScstnct/XAybpjPNWmU6EwCgqz8g
Cl0W8bjvR3bL3Tezl/UmK0o=
=pSD+
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050114024656.GA66730>