linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:15:52 +0100	[thread overview]
Message-ID: <04cc01c62856$ff18c630$9d00a8c0@dcccs> (raw)
In-Reply-To: 17378.40767.339455.85486@cse.unsw.edu.au


----- 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?

It is internal.
The external bitmap is not works for me, because on the boot, only the NFS
is reachable, and it cause crash.

(note: this is raid4 not raid5!)

>
> 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?

It is something, i will find it one minute! :-)

>
> NeilBrown


  reply	other threads:[~2006-02-03  0:15 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++ [this message]
     [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++
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='04cc01c62856$ff18c630$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 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).