Your message dated Wed, 30 May 2007 04:21:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line problem solved in kernel 2.6.21
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: atop
Version: 1.16-2
Severity: normal
I have two SATA disks, sda and sdb. atop always shows both of them as
100% (or sometimes 98%-101%) busy, even when the disks are idle, and
atop also shows their read and write counts as close to zero.
I run a custom kernel, that includes the atopcnt and atopacct
patches. I also use EVMS to manage my root volume, which is on a
raid1 array that uses both sda and sdb. So (as I understand it), the
device mapper module "owns" /dev/sda and /dev/sdb. Maybe relevant.
Thanks,
Andrew.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (300, 'unstable'), (200, 'stable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages atop depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libncurses5 5.5-2 Shared libraries for terminal hand
ii logrotate 3.7.1-3 Log rotation utility
ii zlib1g 1:1.2.3-13 compression library - runtime
atop recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
> I have two SATA disks, sda and sdb. atop always shows both of them as
> 100% (or sometimes 98%-101%) busy, even when the disks are idle, and
> atop also shows their read and write counts as close to zero.
I just upgraded my kernel to 2.6.21, and this problem has gone away. I'm
closing this bug report. A.
--- End Message ---
