From: Eddy Ilg|univation <eddy.ilg@univation.de>
To: linux-raid@vger.kernel.org
Subject: Determine resync direction from syslog?
Date: Mon, 21 Jan 2013 21:33:20 +0100 [thread overview]
Message-ID: <50FDA610.6030702@univation.de> (raw)
Hi,
here's a somewhat funny situation:
A drive (/dev/sdb) of a RAID1 with damaged superblock is attached to a
laptop. Someone stupid attaches another drive (/dev/sdc) with a very old
backup mirror of /dev/sdb. And -
the raid starts to sync:
Jan 21 20:46:32 localhost kernel: [ 7789.680603] md: bind<sdc1>
Jan 21 20:46:32 localhost kernel: [ 7789.681358] md: bind<sdc2>
Jan 21 20:46:32 localhost kernel: [ 7789.685163] RAID1 conf printout:
Jan 21 20:46:32 localhost kernel: [ 7789.685168] --- wd:1 rd:2
Jan 21 20:46:32 localhost kernel: [ 7789.685173] disk 0, wo:1, o:1,
dev:sdc1
Jan 21 20:46:32 localhost kernel: [ 7789.685178] disk 1, wo:0, o:1,
dev:sdb1
Jan 21 20:46:32 localhost kernel: [ 7789.685387] md: recovery of RAID
array md0
Jan 21 20:46:32 localhost kernel: [ 7789.685392] md: minimum
_guaranteed_ speed: 1000 KB/sec/disk.
Jan 21 20:46:32 localhost kernel: [ 7789.685396] md: using maximum
available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Jan 21 20:46:32 localhost kernel: [ 7789.685402] md: using 128k window,
over a total of 3903680 blocks.
Jan 21 20:46:32 localhost kernel: [ 7789.685707] RAID1 conf printout:
Jan 21 20:46:32 localhost kernel: [ 7789.685712] --- wd:1 rd:2
Jan 21 20:46:32 localhost kernel: [ 7789.685717] disk 0, wo:1, o:1,
dev:sdc2
Jan 21 20:46:32 localhost kernel: [ 7789.685721] disk 1, wo:0, o:1,
dev:sdb2
Jan 21 20:46:32 localhost kernel: [ 7789.685819] md: delaying recovery
of md1 until md0 has finished (they share one or more physical units)
Jan 21 20:50:01 localhost kernel: [ 7997.625245] md: md0: recovery done.
Jan 21 20:50:01 localhost kernel: [ 7997.723416] md: recovery of RAID
array md1
Jan 21 20:50:01 localhost kernel: [ 7997.723421] md: minimum
_guaranteed_ speed: 1000 KB/sec/disk.
Jan 21 20:50:01 localhost kernel: [ 7997.723425] md: using maximum
available idle IO bandwidth (but not more than 200000 KB/sec) for recovery.
Jan 21 20:50:01 localhost kernel: [ 7997.723432] md: using 128k window,
over a total of 191454528 blocks.
Which direction did the sync go?
Best regards,
Eddy Ilg
reply other threads:[~2013-01-21 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=50FDA610.6030702@univation.de \
--to=eddy.ilg@univation.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).