Bug 106194

Summary: 'systat -if' display bug
Product: Base System Reporter: Alan Amesbury <amesbury>
Component: amd64Assignee: Yar Tikhiy <yar>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 6.1-RELEASE   
Hardware: Any   
OS: Any   

Description Alan Amesbury 2006-12-02 03:40:03 UTC
For large amounts of total data, FreeBSD/amd64's 'systat -if' changes units
and appears to report in bits.  This is an example screenshot:

                    /0   /1   /2   /3   /4   /5   /6   /7   /8   /9   /10
     Load Average   |||| 

      Interface           Traffic               Peak                Total


            lo0  in      0.000 KB/s          0.000 KB/s            9.832 KB
                 out     0.000 KB/s          0.000 KB/s            9.832 KB

           bge1  in     90.720 MB/s        101.412 MB/s     2903082122259256.000 b
                 out     0.000 KB/s          0.000 KB/s            0.244 KB

           bge0  in      0.025 KB/s          0.395 KB/s          286.027 MB
                 out     0.065 KB/s          0.451 KB/s          406.052 MB


The host in question has been up about 50 days, so it's hard to say exactly
when this display bug gets tickled.  I'm pretty sure it's displaying in bits
because a) the small "b" is a good hint, and more importantly b) there's no
way this host has seen 2600+TB in only 50 days.  362885265282407 bytes (or
around 330TB) is a believeable number, however.

Fix: 

I'm not sure, but I think this might have something to do with the stuff
around line 123 of

	src/usr.bin/systat/ifstat.c,v 1.2 2004/03/09 11:57:27 dwmalone Exp


The FreeBSD/i386 version doesn't exhibit this behavior, but the counter
appears to simply wrap at 4GB anyway.  I suspect that's a limitation of
the architecture, though.

Please let me know if you need additional information.
How-To-Repeat: Pass multiple terabytes through an interface.  Watch systat's counter.
Comment 1 Yar Tikhiy freebsd_committer freebsd_triage 2007-01-05 13:27:21 UTC
State Changed
From-To: open->closed

This bug has already been reported and fixed. 
6.2-RELEASE will be free of it.  See also PR 99731. 


Comment 2 Yar Tikhiy freebsd_committer freebsd_triage 2007-01-05 13:27:21 UTC
Responsible Changed
From-To: freebsd-amd64->yar

This bug has already been reported and fixed. 
6.2-RELEASE will be free of it.  See also PR 99731.