Re: [PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical units with md2!
Folks,
I won't try and invent a patch(1) for this, but might I suggest changing:
md: serializing resync, md%d has shares one or more physical units with
md%d!\n
to
md: serializing resync, md%d shares one or more disk drives with md%d.
Array performance may suffer.\n
Regards,
Ruth
At 12:49 AM 11/20/00, you wrote:
> the attached patch, modifies a warning message in md.c which seems to
> often cause confusion - the following email includes one example
> there-of (there have been others over the months).
> > What it means is that some partititions in md1 and md2 are on the same
> disk,
> > and that the md-code will not do the reconstruction of these arrays in
> > parallel [of course, for performance reasons].
> >
>
>
>--- ./drivers/md/md.c 2000/11/20 00:33:08 1.2
>+++ ./drivers/md/md.c 2000/11/20 00:44:19 1.3
>@@ -3279,7 +3279,7 @@
> if (mddev2 == mddev)
> continue;
> if (mddev2->curr_resync && match_mddev_units(mddev,mddev2)) {
>- printk(KERN_INFO "md: serializing resync, md%d has
>overlapping physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
>+ printk(KERN_INFO "md: serializing resync, md%d has
>shares one or more physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
> serialize = 1;
> break;
> }
>-
--
Ruth
Ivimey-Cook [EMAIL PROTECTED]
Technical
Author, ARM Ltd [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
[PATCH] Re: What is 2.4.0-test10: md1 has overlapping physical units with md2!
Linus, Ingo:
the attached patch, modifies a warning message in md.c which seems to
often cause confusion - the following email includes one example
there-of (there have been others over the months).
Hopefully the new text is clearer.
(patch against 2.4.0-test11-pre7)
NeilBrown
On Sunday November 19, [EMAIL PROTECTED] wrote:
> On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote:
> > 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]).
>
> > Nov 18 16:31:02 mwg kernel: md: serializing resync, md1 has overlapping physical
>units with md2!
>
> Nope, nothing to worry about -- it's just a bad choice of wording ;)
>
> What it means is that some partititions in md1 and md2 are on the same disk,
> and that the md-code will not do the reconstruction of these arrays in
> parallel [of course, for performance reasons].
>
--- ./drivers/md/md.c 2000/11/20 00:33:08 1.2
+++ ./drivers/md/md.c 2000/11/20 00:44:19 1.3
@@ -3279,7 +3279,7 @@
if (mddev2 == mddev)
continue;
if (mddev2->curr_resync && match_mddev_units(mddev,mddev2)) {
- printk(KERN_INFO "md: serializing resync, md%d has overlapping
physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
+ printk(KERN_INFO "md: serializing resync, md%d has shares one
+or more physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
serialize = 1;
break;
}
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Re: What is 2.4.0-test10: md1 has overlapping physical units with md2!
On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote: > 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]). > Nov 18 16:31:02 mwg kernel: md: serializing resync, md1 has overlapping physical >units with md2! Nope, nothing to worry about -- it's just a bad choice of wording ;) What it means is that some partititions in md1 and md2 are on the same disk, and that the md-code will not do the reconstruction of these arrays in parallel [of course, for performance reasons]. Regards, -- Jasper Spaans <[EMAIL PROTECTED]> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: What is 2.4.0-test10: md1 has overlapping physical units with md2!
On Sun, Nov 19, 2000 at 03:39:43AM -0800, George Garvey wrote: > 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]). Nothing to worry. (I got worried also when I saw it the first time) > Nov 18 16:31:02 mwg kernel: md: serializing resync, md0 has overlapping physical units with md2! It is perhaps poorly worded -- multiple MD "devices" using same physical devices, although they are not on overlapped partitions, do get that message. It means simply that if those two were running reconstruction simultaneously, they would cause seeking back&forth over the device. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
What is 2.4.0-test10: md1 has overlapping physical units with md2!
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: 0056] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part3's sb offset: 4194688 [events: 0055] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus0/target0/lun0/part4's sb offset: 24771008 [events: 0058] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part1's sb offset: 524544 [events: 0056] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part3's sb offset: 4194688 [events: 0055] Nov 18 16:31:01 mwg kernel: (read) ide/host0/bus1/target0/lun0/part4's sb offset: 24771008 [events: 0058] 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 Nov 18 16:31:01 mwg kernel: bind Nov 18 16:31:01 mwg kernel: running: Nov 18 16:31:01 mwg kernel: now! Nov 18 16:31:01 mwg kernel: ide/host0/bus1/target0/lun0/part4's event counter: 0058 Nov 18 16:31:01 mwg kernel: ide/host0/bus0/target0/lun0/part4's event counter: 0058 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: 0059](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 10 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: 0059](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 Nov 18 16:31:02 mwg kernel: bind Nov 18 16:31:02 mwg kernel: running: Nov 18 16:31:02 mwg kernel: now! Nov 18 16:31:02 mwg kernel: ide/host0/bus1/target0/lun0/part3's event counter: 0055 Nov 18 16:31:02 mwg kernel: ide/host0/bus0/target0/lun0/part3's event counter: 0055 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: 0056](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: 0056](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 k
