From: George Garvey <tmwg-linuxknl@inxservices.com>
To: linux-kernel@vger.kernel.org
Subject: What is 2.4.0-test10: md1 has overlapping physical units with md2!
Date: Sun, 19 Nov 2000 03:39:43 -0800 [thread overview]
Message-ID: <20001119033943.C935@inxservices.com> (raw)
Is this something to be concerned about? It sounds like a disaster waiting
to happen from the message. This is on 2 systems (with similar disk setups
[same other than size]).
dmesg from bootup:
Nov 18 16:31:01 mwg kernel: md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
Nov 18 16:31:01 mwg kernel: raid1 personality registered
Nov 18 16:31:01 mwg kernel: md.c: sizeof(mdp_super_t) = 4096
Nov 18 16:31:01 mwg kernel: autodetecting RAID arrays
Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part1's sb offset: 524544 [events: 00000056]
Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part3's sb offset: 4194688 [events: 00000055]
Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008 [events: 00000058]
Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part1's sb offset: 524544 [events: 00000056]
Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688 [events: 00000055]
Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008 [events: 00000058]
Nov 18 16:31:01 mwg kernel: autorun ...
Nov 18 16:31:01 mwg kernel: considering ide/host0/bus1/target0/lun0/part4 ...
Nov 18 16:31:01 mwg kernel: adding ide/host0/bus1/target0/lun0/part4 ...
Nov 18 16:31:01 mwg kernel: adding ide/host0/bus0/target0/lun0/part4 ...
Nov 18 16:31:01 mwg kernel: created md2
Nov 18 16:31:01 mwg kernel: bind<ide/host0/bus0/target0/lun0/part4,1>
Nov 18 16:31:01 mwg kernel: bind<ide/host0/bus1/target0/lun0/part4,2>
Nov 18 16:31:01 mwg kernel: running: <ide/host0/bus1/target0/lun0/part4><ide/host0/bus0/target0/lun0/part4>
Nov 18 16:31:01 mwg kernel: now!
Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4's event counter: 00000058
Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4's event counter: 00000058
Nov 18 16:31:01 mwg kernel: md: md2: raid array is not clean -- starting background reconstruction
Nov 18 16:31:01 mwg kernel: md2: max total readahead window set to 124k
Nov 18 16:31:01 mwg kernel: md2: 1 data-disks, max readahead per data-disk: 124k
Nov 18 16:31:01 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part4 operational as mirror 1
Nov 18 16:31:01 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part4 operational as mirror 0
Nov 18 16:31:01 mwg kernel: raid1: raid set md2 not clean; reconstructing mirrors
Nov 18 16:31:01 mwg kernel: raid1: raid set md2 active with 2 out of 2 mirrors
Nov 18 16:31:01 mwg kernel: md: updating md2 RAID superblock on device
Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4 [events: 00000059](write) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008
Nov 18 16:31:01 mwg kernel: md: syncing RAID array md2
Nov 18 16:31:01 mwg kernel: md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.
Nov 18 16:31:01 mwg kernel: md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.
Nov 18 16:31:01 mwg kernel: md: using 124k window, over a total of 24771008 blocks.
Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4 [events: 00000059](write) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008
Nov 18 16:31:01 mwg kernel: .
Nov 18 16:31:01 mwg kernel: considering ide/host0/bus1/target0/lun0/part3 ...
Nov 18 16:31:02 mwg kernel: adding ide/host0/bus1/target0/lun0/part3 ...
Nov 18 16:31:02 mwg kernel: adding ide/host0/bus0/target0/lun0/part3 ...
Nov 18 16:31:02 mwg kernel: created md1
Nov 18 16:31:02 mwg kernel: bind<ide/host0/bus0/target0/lun0/part3,1>
Nov 18 16:31:02 mwg kernel: bind<ide/host0/bus1/target0/lun0/part3,2>
Nov 18 16:31:02 mwg kernel: running: <ide/host0/bus1/target0/lun0/part3><ide/host0/bus0/target0/lun0/part3>
Nov 18 16:31:02 mwg kernel: now!
Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3's event counter: 00000055
Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part3's event counter: 00000055
Nov 18 16:31:02 mwg kernel: md: md1: raid array is not clean -- starting background reconstruction
Nov 18 16:31:02 mwg kernel: md1: max total readahead window set to 124k
Nov 18 16:31:02 mwg kernel: md1: 1 data-disks, max readahead per data-disk: 124k
Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part3 operational as mirror 1
Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part3 operational as mirror 0
Nov 18 16:31:02 mwg kernel: raid1: raid set md1 not clean; reconstructing mirrors
Nov 18 16:31:02 mwg kernel: raid1: raid set md1 active with 2 out of 2 mirrors
Nov 18 16:31:02 mwg kernel: md: updating md1 RAID superblock on device
Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3 [events: 00000056](write) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688
Nov 18 16:31:02 mwg kernel: md: serializing resync, md1 has overlapping physical units with md2!
Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part3 [events: 00000056](write) ide/host0/bus0/target0/lun0/part3's sb offset: 4194688
Nov 18 16:31:02 mwg kernel: .
Nov 18 16:31:02 mwg kernel: considering ide/host0/bus1/target0/lun0/part1 ...
Nov 18 16:31:02 mwg kernel: adding ide/host0/bus1/target0/lun0/part1 ...
Nov 18 16:31:02 mwg kernel: adding ide/host0/bus0/target0/lun0/part1 ...
Nov 18 16:31:02 mwg kernel: created md0
Nov 18 16:31:02 mwg kernel: bind<ide/host0/bus0/target0/lun0/part1,1>
Nov 18 16:31:02 mwg kernel: bind<ide/host0/bus1/target0/lun0/part1,2>
Nov 18 16:31:02 mwg kernel: running: <ide/host0/bus1/target0/lun0/part1><ide/host0/bus0/target0/lun0/part1>
Nov 18 16:31:02 mwg kernel: now!
Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part1's event counter: 00000056
Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part1's event counter: 00000056
Nov 18 16:31:02 mwg kernel: md: md0: raid array is not clean -- starting background reconstruction
Nov 18 16:31:02 mwg kernel: md0: max total readahead window set to 124k
Nov 18 16:31:02 mwg kernel: md0: 1 data-disks, max readahead per data-disk: 124k
Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus1/target0/lun0/part1 operational as mirror 1
Nov 18 16:31:02 mwg kernel: raid1: device ide/host0/bus0/target0/lun0/part1 operational as mirror 0
Nov 18 16:31:02 mwg kernel: raid1: raid set md0 not clean; reconstructing mirrors
Nov 18 16:31:02 mwg kernel: raid1: raid set md0 active with 2 out of 2 mirrors
Nov 18 16:31:02 mwg kernel: md: updating md0 RAID superblock on device
Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part1 [events: 00000057](write) ide/host0/bus1/target0/lun0/part1's sb offset: 524544
Nov 18 16:31:02 mwg kernel: md: serializing resync, md0 has overlapping physical units with md2!
Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part1 [events: 00000057](write) ide/host0/bus0/target0/lun0/part1's sb offset: 524544
Nov 18 16:31:02 mwg kernel: .
Nov 18 16:31:02 mwg kernel: ... autorun DONE.
fdisk:
/dev/hda:
kernel version 132096
Command (m for help):
Disk /dev/hda: 16 heads, 63 sectors, 59554 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 1041 524632+ fd Linux raid autodetect
/dev/hda2 1042 2082 524664 82 Linux swap
/dev/hda3 2083 10405 4194792 fd Linux raid autodetect
/dev/hda4 10406 59554 24771096 fd Linux raid autodetect
Command (m for help):
/dev/hdc:
kernel version 132096
Command (m for help):
Disk /dev/hdc: 16 heads, 63 sectors, 59554 cylinders
Units = cylinders of 1008 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hdc1 1 1041 524632+ fd Linux raid autodetect
/dev/hdc2 1042 2082 524664 82 Linux swap
/dev/hdc3 2083 10405 4194792 fd Linux raid autodetect
/dev/hdc4 10406 59554 24771096 fd Linux raid autodetect
Command (m for help):
/etc/raidtab:
raiddev /dev/md/0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 32
persistent-superblock 1
device /dev/ide/host0/bus0/target0/lun0/part1
raid-disk 0
device /dev/ide/host0/bus1/target0/lun0/part1
raid-disk 1
raiddev /dev/md/1
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 32
persistent-superblock 1
device /dev/ide/host0/bus0/target0/lun0/part3
raid-disk 0
device /dev/ide/host0/bus1/target0/lun0/part3
raid-disk 1
raiddev /dev/md/2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 32
persistent-superblock 1
device /dev/ide/host0/bus0/target0/lun0/part4
raid-disk 0
device /dev/ide/host0/bus1/target0/lun0/part4
raid-disk 1
/proc/mdstat:
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 ide/host0/bus1/target0/lun0/part1[1] ide/host0/bus0/target0/lun0/part1[0]
524544 blocks [2/2] [UU]
md1 : active raid1 ide/host0/bus1/target0/lun0/part3[1] ide/host0/bus0/target0/lun0/part3[0]
4194688 blocks [2/2] [UU]
md2 : active raid1 ide/host0/bus1/target0/lun0/part4[1] ide/host0/bus0/target0/lun0/part4[0]
24771008 blocks [2/2] [UU]
unused devices: <none>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-11-19 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-19 11:39 George Garvey [this message]
2000-11-19 12:51 ` What is 2.4.0-test10: md1 has overlapping physical units with md2! Matti Aarnio
2000-11-19 13:08 ` Jasper Spaans
2000-11-20 0:49 ` [PATCH] " Neil Brown
2000-11-20 12:25 ` Ingo Molnar
2000-11-20 17:15 ` [PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical unitswith md2! Marc Mutz
2000-11-20 14:41 ` [PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical units with md2! Ruth Ivimey-Cook
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=20001119033943.C935@inxservices.com \
--to=tmwg-linuxknl@inxservices.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.