On Mon, 2007-09-03 at 09:34 +0200, Frédéric wrote:
> Bonjour,
>
> Ce week-end, une machine du boulot a vautré bien comme il faut, et j'aimerais
> comprendre pourquoi. On a rebooté la machine le matin, à 10h37...
>
> Dans /var/log/message, on trouve :
>
> Sep 1 21:56:52 in22 -- MARK --
> Sep 1 22:16:53 in22 -- MARK --
> Sep 1 22:36:53 in22 -- MARK --
> Sep 1 22:56:53 in22 -- MARK --
> Sep 1 23:16:53 in22 -- MARK --
> Sep 1 23:36:53 in22 -- MARK --
> Sep 1 23:56:53 in22 -- MARK --
> Sep 2 00:16:54 in22 -- MARK --
> Sep 2 00:36:54 in22 -- MARK --
> Sep 2 00:56:54 in22 -- MARK --
> Sep 2 01:06:01 in22 kernel: md: syncing RAID array md0
> Sep 2 01:06:01 in22 kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
> Sep 2 01:06:01 in22 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
> Sep 2 01:06:01 in22 kernel: md: using 128k window, over a total of 1003904 blocks.
> Sep 2 01:06:01 in22 kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
> Sep 2 01:06:01 in22 kernel: md: delaying resync of md2 until md0 has finished resync (they share one or more physical units)
> Sep 2 01:06:01 in22 kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
> Sep 2 01:06:01 in22 kernel: md: delaying resync of md3 until md0 has finished resync (they share one or more physical units)
> Sep 2 01:06:01 in22 kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
> Sep 2 01:06:01 in22 kernel: md: delaying resync of md2 until md3 has finished resync (they share one or more physical units)
> Sep 2 01:06:39 in22 kernel: md: md0: sync done.
> Sep 2 01:06:39 in22 kernel: md: delaying resync of md2 until md3 has finished resync (they share one or more physical units)
> Sep 2 01:06:39 in22 kernel: md: syncing RAID array md1
> Sep 2 01:06:39 in22 kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
> Sep 2 01:06:39 in22 kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
> Sep 2 01:06:39 in22 kernel: md: using 128k window, over a total of 7004224 blocks.
> Sep 2 01:06:39 in22 kernel: md: delaying resync of md3 until md1 has finished resync (they share one or more physical units)
> Sep 2 01:06:39 in22 kernel: RAID1 conf printout:
> Sep 2 01:06:39 in22 kernel: --- wd:2 rd:2
> Sep 2 01:06:39 in22 kernel: disk 0, wo:0, o:1, dev:hda1
> Sep 2 01:06:39 in22 kernel: disk 1, wo:0, o:1, dev:hdb1
> (reboot)
?!? Ça alors !! J'ai eu un raid resync parasite exactement au même
moment, et je n'ai pas compris pourquoi (trés étrange, surtout que je
n'ai même pas reçu demail pour me dire que mon raid était
désynchronisé ...)
Sep 2 01:06:01 awak kernel: md: syncing RAID array md0
Sep 2 01:06:01 awak kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Sep 2 01:06:01 awak kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Sep 2 01:06:01 awak kernel: md: using 128k window, over a total of 48064 blocks.
Sep 2 01:06:01 awak kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
Sep 2 01:06:01 awak kernel: md: delaying resync of md2 until md0 has finished resync (they share one or more physical units)
Sep 2 01:06:05 awak kernel: md: md0: sync done.
Sep 2 01:06:05 awak kernel: RAID1 conf printout:
Sep 2 01:06:05 awak kernel: --- wd:3 rd:3
Sep 2 01:06:05 awak kernel: disk 0, wo:0, o:1, dev:hda1
Sep 2 01:06:05 awak kernel: disk 1, wo:0, o:1, dev:hde1
Sep 2 01:06:05 awak kernel: disk 2, wo:0, o:1, dev:hdc1
Sep 2 01:06:05 awak kernel: md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
Sep 2 01:06:05 awak kernel: md: syncing RAID array md1
Sep 2 01:06:05 awak kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Sep 2 01:06:05 awak kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Sep 2 01:06:05 awak kernel: md: using 128k window, over a total of 10000384 blocks.
Bizarre que ça arrive quasi en même temps ... se serait-on fait
rootkiter ?
Xav
