I have a couple of OpenVZ containers configured as NFS clients connecting to a FreeBSD server. (FEATURES="nfsn " in the /etc/vz/nnn.conf file)
The mounts use NFSv3 with file-locking enabled.
I am using pve-kernel-2.6.32-4-pve. This setup worked fine with version 2.6.32-30 and earlier of the package. However, since upgrading to kernel 2.6.32-32, NFS file locking has become broken. I am unable to establish a lock on any files in the NFS mounts. I downloaded 2.6.32-31 from pvetest and installed it manually, but it was also broken. It appears that the problematic change occurred between 2.6.32-30 and 2.6.32-31.
Based on the changelog of the PVE kernel, it looks like the problematic change happened upstream in Debian. I tried linux-image-2.6.32-5-openvz-amd64_2.6.32-31_amd64.deb from squeeze and it seems to have the problem as well, which supports that theory. Unfortunately, I can't seem to find a copy of linux-image-2.6.32-5-openvz-amd64_2.6.32-30_amd64.deb or linux-image-2.6.32-5-openvz-amd64_2.6.32-29_amd64.deb anywhere to narrow this down any further.
I had to get the server going again, so I've downgraded back to 2.6.32-30 of the pve kernel for now. I guess the next step is to set up a build environment and start iterating through each of the changes made upstream until I find the problematic one.
Does anyone have any other suggestions... or has anyone experienced anything similar?
The mounts use NFSv3 with file-locking enabled.
I am using pve-kernel-2.6.32-4-pve. This setup worked fine with version 2.6.32-30 and earlier of the package. However, since upgrading to kernel 2.6.32-32, NFS file locking has become broken. I am unable to establish a lock on any files in the NFS mounts. I downloaded 2.6.32-31 from pvetest and installed it manually, but it was also broken. It appears that the problematic change occurred between 2.6.32-30 and 2.6.32-31.
Based on the changelog of the PVE kernel, it looks like the problematic change happened upstream in Debian. I tried linux-image-2.6.32-5-openvz-amd64_2.6.32-31_amd64.deb from squeeze and it seems to have the problem as well, which supports that theory. Unfortunately, I can't seem to find a copy of linux-image-2.6.32-5-openvz-amd64_2.6.32-30_amd64.deb or linux-image-2.6.32-5-openvz-amd64_2.6.32-29_amd64.deb anywhere to narrow this down any further.
I had to get the server going again, so I've downgraded back to 2.6.32-30 of the pve kernel for now. I guess the next step is to set up a build environment and start iterating through each of the changes made upstream until I find the problematic one.
Does anyone have any other suggestions... or has anyone experienced anything similar?