VZFASTBOOT does not work!

[gkovacs]

We had an unexpected power loss this evening on one of our Proxmox 3.4 cluster members, and during boot we realized that VZFASTBOOT (starting all guests without quota, then restarting each with quota calculation) does not work anymore, quota calculation is happening before each guest startup.

This essentially means that on a reasonably loaded server it can take an hour or more to boot up, and your guests will be offline during that time.

# cat vz.conf
...
## Disk quota parameters
DISK_QUOTA=yes
VZFASTBOOT=yes
...

# pveversion -v
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-37-pve)
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-31
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[gkovacs]

I wonder if anyone else has noticed this, because if this issue is reproducible, it's already severely impacting anyone who uses Proxmox in a production environment where availability matters.

 

[gkovacs]

We had this issue again today.

Despite setting VZFASTBOOT=yes Proxmox does not start all guests without quota calculation first.

Filed a bugreport on the Proxmox bugzilla:
https://bugzilla.proxmox.com/show_bug.cgi?id=634

 

[gkovacs]

please help with testing

I find it unfortunate that no one responded to this thread, and the bug reported to the Proxmox bugzilla 2 weeks ago is still in NEW status:
https://bugzilla.proxmox.com/show_bug.cgi?id=634

I would like to ask either the Proxmox devs, or someone from the community to test this issue on a non-production server (with at least a couple of big containers on it).

Testing it would require:
- setting VZFASTBOOT=yes in /etc/vz.conf
- resetting the server without clean shutdown (reset switch)
- checking if on reboot the server starts all containers first then stops them one by one for quota (expected behavior) or quota calculation happens right from start while all containers are offline (this is what we experienced)

Thanks!

 

[redmop]

This might be a not fix because proxmox 4.0 is going lxc