Package: sysstat
Version: 8.0.3-1
Severity: normal

Hello!

I've experienced a problem with iostat which might be due a bug:  It seems to 
me as if iostat was completely broken on my system:  On (Linux 2.6.22 amd64) 
I'm getting 
output like that:

garcin:~# iostat 1 1
sda1     0    0 sda2     0    0 sda3     0    0 sdb1     0    0 sdb2     0    0 
sdb3     0    0 sdc1     0    0 sdc2     0    0 sdc3     0    0 sdd1     0    0 
sdd2     0    
0 sdd3     0    0 sde1     0    0 sde2     0    0 sde3     0    0 sdf1     0    
0 sdf2     0    0 sdf3     0    0 sdg1     0    0 sdg2     0    0 sdg3     0    
0 sdh1     
0    0 sdh2     0    0 sdh3     0    0 sdi1     0    0 sdi2     0    0 sdi3     
0    0 sdj1     0    0 sdj2     0    0 sdj3     0    0 sdk1     0    0 sdk2     
0    0 
sdk3     0    0 sdl1   0    0 sdl2     0    0 sdl3     0    0 sdm1     0    0 
sdm2     0    0 sdm3     0    0 sdn1     0    0 sdn2     0    0 sdn3     0    0 
sdo1     0    
0 sdo2     0    0 sdo3 0    0 sdp1     0    0 sdp2     0    0 sdp3     0    0 
sdq1     0    0 sdq2     0    0 sdq3     0    0 sdr1     0    0 sdr2     0    0 
sdr3     0    
0 sds1     0    0 sds2     0    0 sds3     0    0 sdt1     0    0 sdt2     0    
0 sdt3     0    0 sdu1     0    0 sdu2     0    0 sdu3     0    0 sdv1     0    
0 sdv2     
0    0 sdv3     0    0
/dev/md0        /boot
/dev/md1        /dev/.static/dev
/dev/md1        /
/dev/md2        /data
sda1     0    0 sda2     0    0 sda3     0    0 sdb1     0    0 sdb2     0    0 
sdb3     0    0 sdc1     0    0 sdc2     0    0 sdc3     0    0 sdd1     0    0 
sdd2     0    
0 sdd3     0    0 sde1     0    0 sde2     0    0 sde3     0    0 sdf1     0    
0 sdf2     0    0 sdf3     0    0 sdg1     0    0 sdg2     0    0 sdg3     0    
0 sdh1     
0    0 sdh2     0    0 sdh3     0    0 sdi1     0    0 sdi2     0    0 sdi3     
0    0 sdj1     0    0 sdj2     0    0 sdj3     0    0 sdk1     0    0 sdk2     
0    0 
sdk3     0    0 sdl1   0    0 sdl2     0    0 sdl3     0    0 sdm1     0    0 
sdm2     0    0 sdm3     0    0 sdn1     0    0 sdn2     0    0 sdn3     0    0 
sdo1     0    
0 sdo2     0    0 sdo3 0    0 sdp1     0    0 sdp2     0    0 sdp3     0    0 
sdq1     0    0 sdq2     0    0 sdq3     0    0 sdr1     0    0 sdr2     0    0 
sdr3     0    
0 sds1     0    0 sds2     0    0 sds3     0    0 sdt1     0    0 sdt2     0    
0 sdt3     0    0 sdu1     0    0 sdu2     0    0 sdu3     0    0 sdv1     0    
0 sdv2     
0    0 sdv3     0    0

...repeating infinitely...

...while I would expect something like (on i386):

hoeppi:~# iostat 1 1
Linux 2.6.18-5-486 (hoeppi)     12/08/2007

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           1.91    0.07    0.15    0.08    0.00   97.79

Device:            tps   Blk_read/s   Blk_wrtn/s   Blk_read   Blk_wrtn
sda               0.56         6.08        20.57    2031403    6872912

I tried both 7.0.0-4 and 8.0.3-1, the result was the same.

Any ideas what is happening here?  Is my kernel too new?  Or am I just doing 
something wrong?

Thank you and kind regards,

Thiemo Nagel

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable'), (200, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-e18-tn1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages sysstat depends on:
ii  bzip2                  1.0.3-6           high-quality block-sorting file co
ii  debconf [debconf-2.0]  1.5.11            Debian configuration management sy
ii  libc6                  2.3.6.ds1-13etch2 GNU C Library: Shared libraries
ii  lsb-base               3.1-23.2etch1     Linux Standard Base 3.1 init scrip
ii  ucf                    2.0020            Update Configuration File: preserv

Versions of packages sysstat recommends:
ii  cron                          3.0pl1-100 management of regular background p

-- debconf information:
  sysstat/enable: false
  sysstat/remove_files: true



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to