Open derekslenk opened 10 years ago
Thanks for providing the URL - it looks like no disk i/o metrics are being reported, which likely means we're not able to read from /proc/diskstats
to collect those metrics.
Mind SSH-ing onto your server and running "cat /proc/diskstats"?
This is hosted with Linode. xvda is the / mount
1 0 ram0 0 0 0 0 0 0 0 0 0 0 0 1 1 ram1 0 0 0 0 0 0 0 0 0 0 0 1 2 ram2 0 0 0 0 0 0 0 0 0 0 0 1 3 ram3 0 0 0 0 0 0 0 0 0 0 0 1 4 ram4 0 0 0 0 0 0 0 0 0 0 0 1 5 ram5 0 0 0 0 0 0 0 0 0 0 0 1 6 ram6 0 0 0 0 0 0 0 0 0 0 0 1 7 ram7 0 0 0 0 0 0 0 0 0 0 0 1 8 ram8 0 0 0 0 0 0 0 0 0 0 0 1 9 ram9 0 0 0 0 0 0 0 0 0 0 0 1 10 ram10 0 0 0 0 0 0 0 0 0 0 0 1 11 ram11 0 0 0 0 0 0 0 0 0 0 0 1 12 ram12 0 0 0 0 0 0 0 0 0 0 0 1 13 ram13 0 0 0 0 0 0 0 0 0 0 0 1 14 ram14 0 0 0 0 0 0 0 0 0 0 0 1 15 ram15 0 0 0 0 0 0 0 0 0 0 0 7 0 loop0 0 0 0 0 0 0 0 0 0 0 0 7 1 loop1 0 0 0 0 0 0 0 0 0 0 0 7 2 loop2 0 0 0 0 0 0 0 0 0 0 0 7 3 loop3 0 0 0 0 0 0 0 0 0 0 0 7 4 loop4 0 0 0 0 0 0 0 0 0 0 0 7 5 loop5 0 0 0 0 0 0 0 0 0 0 0 7 6 loop6 0 0 0 0 0 0 0 0 0 0 0 7 7 loop7 0 0 0 0 0 0 0 0 0 0 0 43 0 nbd0 0 0 0 0 0 0 0 0 0 0 0 43 1 nbd1 0 0 0 0 0 0 0 0 0 0 0 43 2 nbd2 0 0 0 0 0 0 0 0 0 0 0 43 3 nbd3 0 0 0 0 0 0 0 0 0 0 0 43 4 nbd4 0 0 0 0 0 0 0 0 0 0 0 43 5 nbd5 0 0 0 0 0 0 0 0 0 0 0 43 6 nbd6 0 0 0 0 0 0 0 0 0 0 0 43 7 nbd7 0 0 0 0 0 0 0 0 0 0 0 43 8 nbd8 0 0 0 0 0 0 0 0 0 0 0 43 9 nbd9 0 0 0 0 0 0 0 0 0 0 0 43 10 nbd10 0 0 0 0 0 0 0 0 0 0 0 43 11 nbd11 0 0 0 0 0 0 0 0 0 0 0 43 12 nbd12 0 0 0 0 0 0 0 0 0 0 0 43 13 nbd13 0 0 0 0 0 0 0 0 0 0 0 43 14 nbd14 0 0 0 0 0 0 0 0 0 0 0 43 15 nbd15 0 0 0 0 0 0 0 0 0 0 0 202 0 xvda 219126 2055 6800834 3541780 1882725 1458432 49283600 20487523 0 1769796 24034640 202 16 xvdb 48352 250312 2390856 483656 37561 341910 3036112 4769813 0 273343 5254010 202 32 xvdc 85 0 680 846 0 0 0 0 0 843 843 9 0 md0 0 0 0 0 0 0 0 0 0 0 0
Having the same problem... I use md raid for /. Here are my stats:
jonathanfisher@blockparty ~ $ sudo cat /proc/diskstats
1 0 ram0 0 0 0 0 0 0 0 0 0 0 0
1 1 ram1 0 0 0 0 0 0 0 0 0 0 0
1 2 ram2 0 0 0 0 0 0 0 0 0 0 0
1 3 ram3 0 0 0 0 0 0 0 0 0 0 0
1 4 ram4 0 0 0 0 0 0 0 0 0 0 0
1 5 ram5 0 0 0 0 0 0 0 0 0 0 0
1 6 ram6 0 0 0 0 0 0 0 0 0 0 0
1 7 ram7 0 0 0 0 0 0 0 0 0 0 0
1 8 ram8 0 0 0 0 0 0 0 0 0 0 0
1 9 ram9 0 0 0 0 0 0 0 0 0 0 0
1 10 ram10 0 0 0 0 0 0 0 0 0 0 0
1 11 ram11 0 0 0 0 0 0 0 0 0 0 0
1 12 ram12 0 0 0 0 0 0 0 0 0 0 0
1 13 ram13 0 0 0 0 0 0 0 0 0 0 0
1 14 ram14 0 0 0 0 0 0 0 0 0 0 0
1 15 ram15 0 0 0 0 0 0 0 0 0 0 0
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
8 16 sdb 143809 30607 12116220 230792 282972 1461337 713424356 245540 0 213536 476260
8 17 sdb1 143641 30607 12114876 230784 161869 1461337 713424356 126748 0 96084 357468
8 0 sda 135932 28316 12003889 206148 274170 1461154 713517756 243456 0 207400 449532
8 1 sda1 135764 28316 12002545 206140 153067 1461154 713517756 128384 0 93492 334456
9 0 md0 315051 0 24116753 0 1920795 0 1426942112 0 0 0 0
259 0 md0p1 0 0 0 0 0 0 0 0 0 0 0
259 1 md0p2 0 0 0 0 0 0 0 0 0 0 0
259 2 md0p5 0 0 0 0 0 0 0 0 0 0 0
@itsderek23 what columns is scout looking at?
http://slenk.com:5555
Disk utlization is actually at 39%, but always shows 0.
Debian 7 x64