Fragen zu Kernel Logeinträgen

Mordor

Mordor

Registered User
Hallo zusammen
Seit kurzen bin ich von einem vServer zu einem Dedizierten Server bei Hetzner umgestiegen, und kenne mich mit den Kernel Logeinträgen noch nicht wirklich aus.
Als ich Heute über die Munin-Seite geflogen bin, ist mir aufgefallen, dass in der Nacht die CPU-Last in einem Maase angestiegen ist, wie es eigentlich nicht sein sollte. Der Server läuft noch im Testbetrieb, deshalb sollten die hohe CPU-Last eben nicht sein. Daraufhin habe ich die Logfiles durchforstet, und bin auf folgende Einträge gestossen, die zur betreffenden Uhrzeit erstellt wurden:
Code: 
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: syncing RAID array md0
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: using 128k window, over a total of 4096448 blocks.
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md3 until md2 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md4 until md3 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md3 until md2 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md5 until md3 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md3 until md2 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
Oct  7 01:06:01 Debian-40-etch-32-minimal kernel: md: delaying resync of md4 until md5 has finished resync (they share one or more physical units)
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: md0: sync done.
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: delaying resync of md4 until md5 has finished resync (they share one or more physical units)
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: delaying resync of md2 until md1 has finished resync (they share one or more physical units)
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: syncing RAID array md1
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: using 128k window, over a total of 1028096 blocks.
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: delaying resync of md3 until md2 has finished resync (they share one or more physical units)
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: md: delaying resync of md5 until md3 has finished resync (they share one or more physical units)
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel: RAID1 conf printout:
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel:  --- wd:2 rd:2
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel:  disk 0, wo:0, o:1, dev:sda1
Oct  7 01:06:53 Debian-40-etch-32-minimal kernel:  disk 1, wo:0, o:1, dev:sdb1
Oct  7 01:07:06 Debian-40-etch-32-minimal kernel: md: md1: sync done.
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: delaying resync of md5 until md3 has finished resync (they share one or more physical units)
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: delaying resync of md3 until md2 has finished resync (they share one or more physical units)
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: syncing RAID array md2
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: using 128k window, over a total of 20731776 blocks.
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: md: delaying resync of md4 until md5 has finished resync (they share one or more physical units)
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel: RAID1 conf printout:
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel:  --- wd:2 rd:2
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel:  disk 0, wo:0, o:1, dev:sda2
Oct  7 01:07:07 Debian-40-etch-32-minimal kernel:  disk 1, wo:0, o:1, dev:sdb2
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: md2: sync done.
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: RAID1 conf printout:
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel:  --- wd:2 rd:2
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel:  disk 0, wo:0, o:1, dev:sda3
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel:  disk 1, wo:0, o:1, dev:sdb3
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: delaying resync of md4 until md5 has finished resync (they share one or more physical units)
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: syncing RAID array md3
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: minimum _guaranteed_ reconstruction speed: 1000 KB/sec/disc.
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: using 128k window, over a total of 5124608 blocks.
Oct  7 01:11:54 Debian-40-etch-32-minimal kernel: md: delaying resync of md5 until md3 has finished resync (they share one or more physical units)
Die Frage ist nun, ob das normal ist, und was hier genau passiert?
Er Synct hier anscheinend irgendwas. Weshalb und wodurch wird das ausgelöst?

Zum System:
Debian Etch 32 Bit
Auf Hetzner Rootserver
Software RADI1 mit 5 Partitionen

Danke schon mal im Vorraus
Gruß Mordor
 
Dein Raid 1 synchronisiert gerade die beiden Festplatten. Näheres erfährst du auch mittels:

Code: 
cat /proc/mdstat
 
Was also heisst, dass in Regelmäsigen Abstenden gecheckt wird, ob alles synchron läuft? Denn eigentlich sollte das RAID 1 ja auf beiden Platten gleichzeitig schreiben, also auch die gleichen Daten auf jeder Platte haben.
 
Bei Debian ist an jedem ersten Sonntag im Monat Raid-Check angesagt.

/etc/cron.d/mdadm
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top