From: Bernd Schubert <bernd-schubert@web.de>
To: linux-raid@vger.kernel.org
Subject: messages after server crash
Date: Mon, 11 Nov 2002 15:26:37 +0100 [thread overview]
Message-ID: <200211111526.37325.bernd-schubert@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2778 bytes --]
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 #2: dmesg.out.bz2 --]
[-- Type: application/x-bzip2, Size: 2988 bytes --]
next reply other threads:[~2002-11-11 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 14:26 Bernd Schubert [this message]
2002-11-11 19:58 ` messages after server crash Neil Brown
2002-11-12 16:02 ` Bernd Schubert
2002-11-12 22:30 ` Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200211111526.37325.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).