[PVE-User] New Kernel - 2.6.32-16 (2.6.32-79) - pvetest
Michael Rasmussen
mir at miras.org
Thu Oct 18 18:14:44 CEST 2012
On Thu, 18 Oct 2012 17:54:47 +0200
Michael Rasmussen <mir at miras.org> wrote:
> Isn't this something which should be easy to solve? All files
> prefixed .nfs are NFS file locks which by nature should not be
> migrated since the only make sense in a specific nodes context.
>
Hi Martin,
Does mounting the NFS share with option nolock solve the problem?
"lock / nolock Selects whether to use the NLM sideband protocol
to lock files on the server. If neither option is
specified (or if lock is specified), NLM locking
is used for this mount point. When using the
nolock option, applications can lock files, but
such locks provide exclusion only against other
applications running on the same client. Remote
applications are not affected by these locks.
NLM locking must be disabled with the nolock
option when using NFS to mount /var because /var
contains files used by the NLM implementation on
Linux. Using the nolock option is also
required when mounting exports on NFS servers
that do not support the NLM protocol.
"
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael <at> rasmussen <dot> cc
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xD3C9A00E
mir <at> datanom <dot> net
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE501F51C
mir <at> miras <dot> org
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E80917
--------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20121018/96e52281/attachment.sig>
More information about the pve-user
mailing list