Changes

Jump to: navigation, search

UBC failcnt reset

364 bytes added, 10:25, 16 February 2017
m
bugzilla.openvz.org -> bugs.openvz.org
UBC failcnts are stored for the duration of the uptime of your container. Thus, restarting the container resets the counts.
The problem here is tcp time wait buckets can still be there after a container is stopped. You can check that by seeing the <code>held</code> column for <code>kmemsize</code> parameter. If it is not zero, that means you have to wait about 5 minutes in order to time wait buckets to expire, and the corresponding beancounter to be uncharged.
If you still see failcnt not reset to 0 after more than 5 minutes after container is stopped, your kernel was likely compiled with CONFIG_UBC_KEEP_UNUSED=y, and in that case you'll have to switch off this option if you want to reset beancounters when container is restarted.
If you're sure your kernel was NOT compiled with the above option and it's not resetting failcnt after 5 minutes, it means there is a bug in UBC code. Please file a detailed [[bug report]] to [http://bugzillabugs.openvz.org bugzillabugs.openvz.org]
== Bash vzubc == {{Man|vzubc|8}} is a tool to show user beancounters in a decent human readable form. Its relative mode (option -r or --relative) is used to show the failcnt difference from the previous run. vzubc is available in vzctl package since vzctl-3.0.27. == Alternative bash script ==
This script can show the failcount deltas for one or all containers since last reset, and reset the failcounts for one or all containers.
=== beanc source code ===
<div class="mw-collapsible mw-collapsed">Click a link to the right to view the code →<source lang=bashclass="mw-collapsible-content">
#!/bin/bash
#####################################################################################################################
esac
</source>
 == Tool == See {{Bug|1298}}.</div>
== External links ==

Navigation menu