From: NeilBrown <neilb@suse.de>
To: Igor M Podlesny <for.poige+lsr@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync
Date: Mon, 28 May 2012 11:45:50 +1000 [thread overview]
Message-ID: <20120528114550.417ae379@notabene.brown> (raw)
In-Reply-To: <CA+sTkh67PwRkuYyXMRHUFmJUmC==9KFJNnpK+SsAhCTB-48UOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2378 bytes --]
On Mon, 28 May 2012 00:10:33 +0800 Igor M Podlesny <for.poige+lsr@gmail.com>
wrote:
> On 27 May 2012 20:00, NeilBrown <neilb@suse.de> wrote:
> > On Sun, 27 May 2012 19:32:40 +0800 Igor M Podlesny <for.poige+lsr@gmail.com>
> > 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.
>
> > Did that arrays still have their bitmaps?
>
> I still have that RAID-6, yep:
>
> md127 : active raid6 sdg5[2] sdf5[6] sde5[7] sda5[0] sdd5[3] sdc5[1]
> 1071984640 blocks super 1.0 level 6, 1024k chunk, algorithm 2
> [6/6] [UUUUUU]
> bitmap: 0/1 pages [0KB], 131072KB chunk
>
> > Where they degraded?
>
> No way.
>
> > How many bits were set in the bitmaps (probably too late to check now)?
>
> Please see above. And the RAID-5 one was recently dismissed, alas.
>
> > Is it reproducable ? ... OK, I don't really expect you to try to reproduce
> > it, but if you could that would be awesome!
>
> Well, might be VirtualBox would allow for such kind of experiment, dunno. )
>
> 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.
NeilBrown
>
> --
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-05-28 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 11:32 Hi! Strange issue with LSR -- bitmaps hadn't been used during 2 of 3 RAIDs resync Igor M Podlesny
2012-05-27 12:00 ` NeilBrown
2012-05-27 16:10 ` Igor M Podlesny
2012-05-28 1:45 ` NeilBrown [this message]
2012-05-28 2:37 ` Igor M Podlesny
2012-05-28 2:54 ` NeilBrown
2012-05-28 4:03 ` Igor M Podlesny
2012-06-20 2:49 ` Igor M Podlesny
2012-06-26 6:18 ` NeilBrown
2012-06-26 8:55 ` Igor M Podlesny
2012-06-26 9:22 ` Igor M Podlesny
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=20120528114550.417ae379@notabene.brown \
--to=neilb@suse.de \
--cc=for.poige+lsr@gmail.com \
--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).