From: "JaniD++" <djani22@dynamicweb.hu>
To: linux-raid@vger.kernel.org
Subject: Fw: raid 4, and bitmap.
Date: Fri, 3 Feb 2006 01:25:12 +0100 [thread overview]
Message-ID: <04e601c62858$4c790330$9d00a8c0@dcccs> (raw)
----- Original Message -----
From: "JaniD++" <djani22@dynamicweb.hu>
To: "Neil Brown" <neilb@suse.de>
Sent: Friday, February 03, 2006 1:20 AM
Subject: Re: raid 4, and bitmap.
>
> ----- Original Message -----
> From: "Neil Brown" <neilb@suse.de>
> To: "JaniD++" <djani22@dynamicweb.hu>
> Cc: <linux-raid@vger.kernel.org>
> Sent: Friday, February 03, 2006 1:09 AM
> Subject: Re: raid 4, and bitmap.
>
>
> > On Friday February 3, djani22@dynamicweb.hu wrote:
> > > Hello, list, Neil,
> > >
> > > I try to add bitmaps to raid4, and mdadm is done this fine.
> > > In the /proc/mdstat shows this, and it is really works well.
> > >
> > > But on reboot, the kernel drops the bitmap(, and resync the entire
array
> if
> > > it is unclean). :(
> > >
> > > It is still uncomplete now? (2.6.16-rc1)
> >
> >
> > It is an 'internal' bitmap, or is the bitmap in a file?
> >
> > If the bitmap is in a file, you need to me sure that the file is
> > provided by mdadm when the array is assembled - using in-kernel
> > autodetect won't work.
> >
> > 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. :(
>
> Cheers,
> Janos
>
> >
> > NeilBrown
>
reply other threads:[~2006-02-03 0:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='04e601c62858$4c790330$9d00a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--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 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.