Bug#539154: mdadm: Keeps detecting NewArray events as fast as the CPU goes
Sami Liedes
sliedes at cc.hut.fi
Thu Aug 6 22:08:05 UTC 2009
I have the same problem, except I'm not sure it spams syslog. Found it
taking 100% CPU. strace looks like this:
------------------------------------------------------------
open("/dev/md0", O_RDONLY) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
ioctl(4, 0x80480911, 0x7fffe1048660) = 0
close(4) = 0
open("/dev/md0", O_RDONLY) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
ioctl(4, 0x80480911, 0x7fffe1048660) = 0
close(4) = 0
open("/dev/md0", O_RDONLY) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
ioctl(4, 0x80480911, 0x7fffe1048660) = 0
close(4) = 0
[... ad infinitum]
------------------------------------------------------------
Here too I have a raid 0 array with one disk removed.
Sami
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mdadm-devel/attachments/20090807/68baa288/attachment.pgp>
More information about the pkg-mdadm-devel
mailing list