| Are dcachesize values supposed to be 0's? [message #27059] |
Thu, 07 February 2008 17:20  |
 |
dowdle
Messages: 261
Registered: December 2005
Location: Bozeman, Montana
|
Senior Member |
|
|
I haven't had any problems as a result of this... but looking at the UBC output from a few different machines I notice that several of them have 0 values in the held and maxheld values for dcachesize. This seems odd. Should dcachesize have 0 values?
There didn't seem to be any pattern to when it would be zero and when it wouldn't be 0. I have two machines that are exactly alike in hardware and software... and even VPSes... and one has non-0 values for dcachesize and the other has 0's.
Example output from two similar hardware nodes:
[root@backup1 ~]# grep dcachesize /proc/user_beancounters
dcachesize 65844 90801 9985491 10285056 0
dcachesize 1696690 1863838 2147483647 2147483647 0
[root@backup2 ~]# grep dcachesize /proc/user_beancounters
dcachesize 0 0 9985491 10285056 0
dcachesize 0 0 2147483647 2147483647 0
Questions:
1) Should the held and maxheld columns for dcachesize ever be 0
2) If yes to #1, why?
3) If no to #2, want me to file a bug report?
--
TYL, Scott Dowdle
Belgrade, Montana, USA
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
