*KNOWN ISSUE* VZquota and Shared VEs with NFS [message #13550] |
Tue, 29 May 2007 17:29 |
seanfulton
Messages: 105 Registered: May 2007
|
Senior Member |
|
|
I am having a problem using an NFS shared drive with OpenVZ. What I want to do is have a single NFS share that is mounted on three machines, weba, webb and webc.
weba will run vz 1-50, while webb will run vz51-100. webc will take-over for either a or b should a or b fail.
I followed the instructions in http://wiki.openvz.org/HA_cluster_with_DRBD_and_Heartbeat#In stalling_the_two_nodes
The problem I am having is #1, the quota info on weba is messed up--it shows minus disk space. #2, when I try to run a vz off of web2, it tells me:
Starting VE ...
vzquota : (error) can't lock quota file, some quota operations are performing for id 7003
vzquota on failed [7]
Even though vz7003 is not running on any of the machines.
It looks to me like an NFS lock problem, but none of the other files that are shared are having the same problem.
Any ideas or insight would be appreciated.
sean
[Updated on: Mon, 04 June 2007 06:53] by Moderator Report message to a moderator
|
|
|
|
|
|
|
Re: *KNOWN ISSUE* VZquota and Shared VEs with NFS [message #13728 is a reply to message #13726] |
Mon, 04 June 2007 12:32 |
seanfulton
Messages: 105 Registered: May 2007
|
Senior Member |
|
|
The article about DRBD just showed me how to set the mounts and links to use VZ on a shared drive.
I am using DRBD on two servers (A and B), but I want them both to actively share the storage along with a third server that will act as a hot stand-by. So A and B share the DRBD drive via NFS, A runs half the VEs, B runs the other half. The drive is also shared out to Machine C which monitors *all* the VEs and will take over for any that fail.
The DRBD article only uses one active server and one stand-by. The DRBD-NFS-HA solution theoretically lets me run two servers with one stand-by.
I was using the stock RHEL kernel. The entire /vz partition was on NFS, and it was the RPM database inside the VE that was corrupted. So yes, it was on the NFS share. Is 34 out yet?
I looked into other ways of sharing network mirrored storage out to the network, specifically GFS, but I couldn't find any good documentation or reports of wide-spread use. The DRBD-NFS-HA solution seems to be in wide-spread use, so I chose that. Using VZ over DRBD provided a means to "share" the VZ data, so I used that as well.
If you know of or can recommend a better setup, I would be glad to try it. The real object here is to have multiple primary servers with one stand-by ready to take-over at any time.
sean
|
|
|
|
|
|
Re: *KNOWN ISSUE* VZquota and Shared VEs with NFS [message #13946 is a reply to message #13933] |
Fri, 08 June 2007 10:59 |
seanfulton
Messages: 105 Registered: May 2007
|
Senior Member |
|
|
OK, well, I'm asking specifically about the NFS problem now. I've discovered strange behavior over an NFS mount having nothing to do with VZ. Writing with CPIO or copy returns errors of that there is no more disk space, when in fact there is *plenty* of space.
This works with the 33 kernel on both machines, and with the drive NFS3 mounted across the network so I suspect it's related to the other issue.
Also, have you any reports of people using GFS or OCFS2 for shared drives with VEs on them?
sean
|
|
|