|
>> Don't think so, I'm running dmesg > dmesg.1-N So far diffs are showing
them
>> to be all the same.
>
> And all this without your cronjob doing the eth2 down/up, right? Or let
> me ask in a different way. Do you think that your problem seems to be
> solved so far until it will show up again?
Yes, this is with the cronjob removed. So yes, I think we are fixed until
the problem shows up again. :) Lets keep our fingers crossed!
btw, you asked earlier how often I was running the cronjob that brough eth2
up and down. At first I was running it 2 times an hour, after the last
problem yesterday I changed it to run every minute.
> Ok, so 6000+ entries expired. How much time did pass between the first
> and the second call of this command and did you run 'ip route flush
> cache' in between?
Hmm, it seems to be back up. Yes, I did run the flush cache since it's part
of the script you gave me.
root@director:~# ./diag2.sh
grep cache /proc/slabinfo
kmem_cache 80 80 244 5 5 1 : 252 126
inet_peer_cache 408 1416 64 23 24 1 : 252 126
ip_dst_cache 18990 22140 192 1008 1107 1 : 252 126
arp_cache 1650 1650 128 55 55 1 : 252 126
dnotify cache 0 0 20 0 0 1 : 252 126
file lock cache 126 126 92 3 3 1 : 252 126
fasync cache 0 0 16 0 0 1 : 252 126
uid_cache 226 226 32 2 2 1 : 252 126
skbuff_head_cache 582 960 192 36 48 1 : 252 126
cdev_cache 1239 1239 64 21 21 1 : 252 126
bdev_cache 118 118 64 2 2 1 : 252 126
mnt_cache 118 118 64 2 2 1 : 252 126
inode_cache 114149 114149 512 16307 16307 1 : 124 62
dentry_cache 116850 116850 128 3895 3895 1 : 252 126
names_cache 57 57 4096 57 57 1 : 60 30
fs_cache 228 354 64 6 6 1 : 252 126
files_cache 173 297 416 27 33 1 : 124 62
-------------------------------------------------
ip -o -s route show cache | wc -l
18226
I haven't changed bitmask yet though.
|
