linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID6 and crashes (reporting back re. --bitmap)
Date: Mon, 14 Jun 2010 09:05:20 +1000	[thread overview]
Message-ID: <20100614090520.2ae5a961@notabene.brown> (raw)
In-Reply-To: <201006131628.35037.bernd.schubert@fastmail.fm>

On Sun, 13 Jun 2010 16:28:34 +0200
Bernd Schubert <bernd.schubert@fastmail.fm> wrote:

> On Friday 11 June 2010, Neil Brown wrote:
> > On Fri, 11 Jun 2010 00:31:57 -0400
> > 
> > "Graham Mitchell" <gmitch@woodlea.com> wrote:
> > > Can you do this on a live array, or can it only be done (as the docs seem
> > > to suggest), with the create, build and grow options?
> > 
> > As 'grow' can (and must) be used on a live array you're question doesn't
> > exactly make sense.
> > Yes: it can be done on a live array.
> 
> While I have done this myself a couple of times, I still do not understand 
> where it takes the disk space for the bitmap journal from? Is this space mdadm 
> reserved for this purpose?

Sort-of.
It uses space that the alignment requirements of the metadata assure us is
otherwise unused.
For v0.90, that is limited to 60K.  For 1.x it is 3K.
With recent kernels it is possible for mdadm to tell the kernel where to put
the bitmap (rather than the kernel *knowing*) so mdadm could use other space
that was reserved when the array was created, but I haven't implemented that
in mdadm yet.

NeilBrown

  reply	other threads:[~2010-06-13 23:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 18:02 RAID6 and crashes Miles Fidelman
2010-06-10 18:57 ` Roman Mamedov
2010-06-10 21:22   ` RAID6 and crashes (reporting back re. --bitmap) Miles Fidelman
2010-06-10 21:41     ` Roman Mamedov
2010-06-10 22:40       ` Miles Fidelman
2010-06-11  2:51         ` Roman Mamedov
2010-06-11  4:31           ` Graham Mitchell
2010-06-11  4:41             ` Roman Mamedov
2010-06-11 12:13               ` Graham Mitchell
2010-06-11  4:42             ` Miles Fidelman
2010-06-11  4:50             ` Neil Brown
2010-06-13 14:28               ` Bernd Schubert
2010-06-13 23:05                 ` Neil Brown [this message]
2010-06-14  9:01                   ` Bernd Schubert
2010-06-14  9:14                   ` Roman Mamedov
2010-06-14  9:47                     ` Neil Brown
2010-06-14 11:53                       ` Roman Mamedov
2010-06-14 21:24                         ` Neil Brown
2010-06-11  4:46           ` Miles Fidelman
2010-06-11  4:55             ` Roman Mamedov
2010-06-11 20:26               ` Miles Fidelman
2010-06-11  5:08             ` Neil Brown
2010-06-11 11:10               ` John Hendrikx
2010-06-11 11:50                 ` Roman Mamedov
2010-06-11 12:29                   ` Graham Mitchell
2010-06-11 12:25                 ` Graham Mitchell

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=20100614090520.2ae5a961@notabene.brown \
    --to=neilb@suse.de \
    --cc=bernd.schubert@fastmail.fm \
    --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).