Hi,
after our server crashed on Friday and Sunday, we can see some strange raid
related messages in the logs (please see the messages below).
Well, the 'delaying resync ...' messages are easy to understand, but are they
related to the 'resync aborted' messages ? At least the /proc/mdstat looks
fine.
The bzip2-output of dmesg (that might give more information about what is
going on) is attached.
So do we have do worry about something going wrong with the software raid ?
Of course, we are a bit worried about the the crashes at all, since this never
happend before.
Thanks in advance,
Bernd
PS: The kernel is a vanilla 2.4.19 with some of Neils NFS-patches that went
into 2.4.20pre1 (all except the tcp-patches).
Nov 10 11:38:31 coulomb kernel: raid5: resync aborted!
Nov 10 11:38:31 coulomb kernel: md: delaying resync of md1 until md0 has
finished resync (they share one or more physical units)
Nov 10 11:38:31 coulomb kernel: md: delaying resync of md2 until md0 has
finished resync (they share one or more physical units)
Nov 10 11:38:31 coulomb kernel: md: delaying resync of md3 until md0 has
finished resync (they share one or more physical units)
Nov 10 11:38:31 coulomb kernel: raid5: resync aborted!
Nov 10 11:38:31 coulomb kernel: md: delaying resync of md1 until md0 has
finished resync (they share one or more physical units)
Nov 10 11:38:31 coulomb kernel: md: delaying resync of md2 until md0 has
finished resync (they share one or more physical units)
Nov 10 11:38:31 coulomb kernel: raid5: resync aborted!
Nov 10 11:38:31 coulomb kernel: md: delaying resync of md1 until md0 has
finished resync (they share one or more physical units)
Nov 10 11:38:31 coulomb kernel: raid5: resync aborted!
Nov 10 11:38:31 coulomb kernel: md: recovery thread got woken up ...
Nov 10 11:38:31 coulomb kernel: md: recovery thread finished ...
Nov 10 11:38:31 coulomb kernel: md: md_do_sync() got signal ... exiting
Nov 10 11:38:31 coulomb kernel: raid5: resync aborted!
coulomb:~ # cat /proc/mdstat
Personalities : [raid5]
read_ahead 1024 sectors
md4 : active raid5 sde8[4] sdd8[3] sdc8[2] sdb8[1] sda8[0]
33960960 blocks level 5, 32k chunk, algorithm 2 [5/5] [UUUUU]
md3 : active raid5 sde7[4] sdd7[3] sdc7[2] sdb7[1] sda7[0]
31261952 blocks level 5, 32k chunk, algorithm 2 [5/5] [UUUUU]
md2 : active raid5 sde6[4] sdd6[3] sdc6[2] sdb6[1] sda6[0]
31261952 blocks level 5, 32k chunk, algorithm 2 [5/5] [UUUUU]
md1 : active raid5 sde5[4] sdd5[3] sdc5[2] sdb5[1] sda5[0]
31261952 blocks level 5, 32k chunk, algorithm 2 [5/5] [UUUUU]
md0 : active raid5 sde1[4] sdd1[3] sdc1[2] sdb1[1] sda1[0]
15614720 blocks level 5, 32k chunk, algorithm 2 [5/5] [UUUUU]
Attachment:
dmesg.out.bz2
Description: BZip2 compressed data
