[Users] vswap question - physpages/oomguarpages

Rene C. openvz at dokbua.com
Thu Jun 21 00:44:06 EDT 2012


I just noticed a couple of containers on one of our  vswap enabled servers
have non-zero failcnt's (user_beancounters)

       uid  resource                     held              maxheld
     barrier                limit              failcnt
     1413:
            physpages                   84873               131166
           0               131072                   61
            oomguarpages                94628               377952
           0  9223372036854775807                    4
     1409:
            physpages                   52986               262155
           0               262144                 1378
            oomguarpages                57155               376725
           0  9223372036854775807                   18

(I've deleted lines with zero failcnt for clarity)

It was my understanding that if a vswap enabled container try to use more
physpages than available it would start "vswapping" - is that what happens
here? Otherwise how can physpages fail?  Is this normal swapping behavior
or a problem?

A second thing is, when I tried to raise the physpages value with vzctl it
again wrote the old "block" values into the vz conf files, i.e.

i.e. before running vzctl the values are like this:
< PHYSPAGES="0:512M"
< SWAPPAGES="0:1024M"

after running vzctl --set 1413 --save --ram 512M --swap 1G the values are
like this:
> PHYSPAGES="0:131072"
> SWAPPAGES="0:262144"

I already opened a bug report on this and I though it had been fixed
already.  Is there some undocumented flag that needs to be provided to
vzctl to get it to write out the values in the easy human readable format?

Regards,
Rene
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://openvz.org/pipermail/users/attachments/20120621/307cedf8/attachment.html


More information about the Users mailing list