All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: Mike Hartman <mike@hartmanipulation.com>
Cc: Wolfgang Denk <wd@denx.de>, linux-raid@vger.kernel.org
Subject: Re: How to initialize "composite" RAID
Date: Sat, 11 Sep 2010 15:09:23 +1000	[thread overview]
Message-ID: <20100911150923.41043519@notabene> (raw)
In-Reply-To: <AANLkTin7T8rsF=XhWYTZyEwUkb5BUzK6dswVoTB-Sbbs@mail.gmail.com>

On Sat, 11 Sep 2010 00:58:21 -0400
Mike Hartman <mike@hartmanipulation.com> wrote:

> > If you add a bitmap (mdadm --grow /dev/md0 --bitmap=internal) after the
> > current resync finished, then any subsequent resync due to an unclean
> > shutdown will be much faster.
> 
> I read somewhere (I think in the wiki) that an intent bitmap only
> works properly on ext2 and ext3 and can cause trouble on other file
> systems. Can I use one on ext4 (what I'm using)? I'm hoping/assuming
> what I read just predates the common use of ext4.

That is completely wrong.  An intent bitmap works properly no matter what
filesystem is on top.
It does impose a small performance penalty for writes which is very
work-load-dependant, and it is not impossible that different filesystems
would suffer more or less from this, but I doubt you would notice.

If you can find it again let me know and I'll try to get it fixed.

> 
> Will I need to remove the bitmap before adding another disk and
> growing the array to use it? If I don't, will it speed up that
> operation any?

You, you will need to remove the bitmap before growing the array.  I really
should fix that but it doesn't seem to rise to the top of my to-do list...

And no, a bitmap would have no effect on a reshape operation even if it were
allowed to be present.

NeilBrown


  reply	other threads:[~2010-09-11  5:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 22:14 How to initialize "composite" RAID Mike Hartman
2010-09-10 22:28 ` Wolfgang Denk
2010-09-10 22:33   ` Mike Hartman
2010-09-10 22:37   ` Neil Brown
2010-09-10 22:45     ` Mike Hartman
2010-09-10 23:07       ` Neil Brown
2010-09-10 23:36         ` Mike Hartman
2010-09-11  0:23           ` Neil Brown
2010-09-11  2:30             ` Mike Hartman
2010-09-11  4:42               ` Neil Brown
2010-09-11  4:58                 ` Mike Hartman
2010-09-11  5:09                   ` Neil Brown [this message]
2010-09-11  5:15                     ` Mike Hartman
2010-09-11 22:13                   ` John Robinson

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=20100911150923.41043519@notabene \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=mike@hartmanipulation.com \
    --cc=wd@denx.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.