From: "JaniD++" <djani22@dynamicweb.hu>
To: Neil Brown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: raid 4, and bitmap.
Date: Fri, 3 Feb 2006 01:31:59 +0100 [thread overview]
Message-ID: <04f401c62859$407f6910$9d00a8c0@dcccs> (raw)
In-Reply-To: 17378.41629.709430.775224@cse.unsw.edu.au
----- Original Message -----
From: "Neil Brown" <neilb@suse.de>
To: "JaniD++" <djani22@dynamicweb.hu>
Cc: <linix-raid@vger.kernel.org>
Sent: Friday, February 03, 2006 1:23 AM
Subject: Re: raid 4, and bitmap.
> On Friday February 3, djani22@dynamicweb.hu wrote:
> > >
> > > If it is an internal bitmap.... it should work.
> > > Are there any kernel messages during boot that might be interesting?
> >
> > Sorry, i did not log this, and i dont want to restart the sync and
system
> > for this.
> > Anyway, i add back the bitmap, and the next crash we will see....
> >
> > I mean this was:
> > "bitmap is only support in raid1.
> > bitmap is removed."
> >
> > But not so sure. :(
>
> Close enough. Here is the fix.
Thanks!
This was fast! :)
Ahh, i almost forget!
The mdadm is sometimes drop "cannot allocate memory" and next try "segfault"
when i try -G --bitmap=internal on 2TB arrays!
And after segfault, the full raid is stops...
Cheers,
Janos
>
> NeilBrown
>
> Signed-off-by: Neil Brown <neilb@suse.de>
>
> ### Diffstat output
> ./drivers/md/md.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff ./drivers/md/md.c~current~ ./drivers/md/md.c
> --- ./drivers/md/md.c~current~ 2006-02-03 08:57:28.000000000 +1100
> +++ ./drivers/md/md.c 2006-02-03 11:22:57.000000000 +1100
> @@ -763,7 +763,8 @@ static int super_90_validate(mddev_t *md
>
> if (sb->state & (1<<MD_SB_BITMAP_PRESENT) &&
> mddev->bitmap_file == NULL) {
> - if (mddev->level != 1 && mddev->level != 5 && mddev->level != 6
> + if (mddev->level != 1 && && mddev->level != 4
> + && mddev->level != 5 && mddev->level != 6
> && mddev->level != 10) {
> /* FIXME use a better test */
> printk(KERN_WARNING "md: bitmaps not supported for this level.\n");
next prev parent reply other threads:[~2006-02-03 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 0:04 raid 4, and bitmap JaniD++
2006-02-03 0:09 ` Neil Brown
2006-02-03 0:15 ` JaniD++
[not found] ` <04d701c62857$9eb02e90$9d00a8c0@dcccs>
2006-02-03 0:26 ` Neil Brown
[not found] ` <17378.41629.709430.775224@cse.unsw.edu.au>
2006-02-03 0:31 ` JaniD++ [this message]
2006-02-04 11:19 ` JaniD++
2006-02-05 23:03 ` Neil Brown
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='04f401c62859$407f6910$9d00a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.