On 28 May 2012 09:45, NeilBrown <neilb@xxxxxxx> wrote: > On Mon, 28 May 2012 00:10:33 +0800 Igor M Podlesny <for.poige+lsr@xxxxxxxxx> > wrote: > >> On 27 May 2012 20:00, NeilBrown <neilb@xxxxxxx> wrote: >> > On Sun, 27 May 2012 19:32:40 +0800 Igor M Podlesny <for.poige+lsr@xxxxxxxxx> >> > wrote: >> >> A power outage has happened to system (which was in "suspend" >> >> state) with RAID-10, RAID-5 and RAID-6. Later on boot, RAID-10 was >> >> fast re-synced using bitmap, but both RAID-5 and RAID-6 were in >> >> auto-readonly mode with resync=DELAYED. When they flipped to >> >> Read-Write, LSR started re-syncing not using bitmaps seemingly. A bug? >> > >> > Maybe. But with so little detail it is hard to say. >> > What made you think the bitmaps weren't being used? >> >> Well, it is reasonable to assume that host being put in suspend >> mode wouldn't have much not synced data at all. RAID-10 had been >> progressing its resync quite fast, it was obvious that it had been >> using bitmaps for that. Moreover — RAID-10 was the most I/O active >> comparing to others, AFAIR. > > Unfortunately vague statements about "it was obvious" or "AFAIR" don't really > help in analysing a situation to find any bugs. > I can only really work with concrete facts. Without them I cannot help. Well, than probably you could tell me how one does find out whether recovery uses WIB, or it doesn't? :-) I mean aside from vague estimating based on watching re-sync progressing and considering overall time it finally took to complete. >> P. s. Oh, and BTW, I see 2.6.18 supplied by RedHat still has the >> bug causing kernel panic when using WIB -- couldn't you please point >> out is it due to they're missing some important bugfix you made later? > > I have no time or interest for submiting bug reports to distros that I don't > use. If the presence of the bug concerns you, I suggest you report it. I thought you could have some recollections bout this rather nasty behavior. It has nothing to do with bug-reports for RedHat since vanilla 2.6.18 for sure has the same bug, and hopefully it has been fixed in later releases -- that was the only thing I was asking you about. But your competent suggestions are also appreciated, of course. -- -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
