"Error in flock(): No locks available" when modifying/adding/deleting a VZ on NFS

Josh North

New Member
Nov 27, 2013
6
0
1
I receive the following error on any actions (modify/add/delete) performed on a VZ running on an NFS share.
Code:
[COLOR=#000000][FONT=tahoma]Error in flock(): No locks available[/FONT][/COLOR]

Also, when inside a running VZ (also on the NFS share) I receive similar errors about file locks.

Here is my environment.
Proxmox 3.1-24
3 host nodes with 4 NIC's. 2 switches in HA pair/trunk. 2 bonded NICs on each box for guest node traffic, 2 bonded NIC's for storage service. Both are also used for management access.

Storage server is a single server right now, eventually will be HA. It is running OpenFiler with NFS share for Proxmox - mostly default options except also has no_root_squash enabled.

This set up has run quite well for about 2 weeks, until this morning when it gave me this error. No changes have been made on host, guest, or storage nodes. All nodes have been hard rebooted since I saw the issue but it persists anyway.

Not sure what other details would be needed.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!