All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <roman@rm.pp.ru>
To: Neil Brown <neilb@suse.de>
Cc: Bernd Schubert <bernd.schubert@fastmail.fm>, linux-raid@vger.kernel.org
Subject: Re: RAID6 and crashes (reporting back re. --bitmap)
Date: Mon, 14 Jun 2010 17:53:27 +0600	[thread overview]
Message-ID: <20100614175327.57f05bb1@natsu> (raw)
In-Reply-To: <20100614194742.4a383a3f@notabene.brown>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

On Mon, 14 Jun 2010 19:47:42 +1000
Neil Brown <neilb@suse.de> wrote:

> When you create an array an specify that a bitmap be added at the same time,
> there is more flexibility for size and location of the bitmap.  It can easily
> be more that 3K in that case.
> 
> So presumably this array was created with a bitmap, rather than created
> without a bitmap and had a bitmap added later with --grow.  Correct?

Yes, as far as I remember. However, it seems a bit unfortunate to have any
significant difference between adding the bitmap right when creating the
array, and adding it later. For that reason, I'd suggest reserving more space
in the metadata than 3K, even if the bitmap isn't requested - and even if it
won't be added later, then that space could prove useful for something else
that might require it later. Maybe 64, 128 or 256K - still miniscule compared
to the array size, and could provide some nice flexibility for the future.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-14 11:53 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
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 [this message]
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=20100614175327.57f05bb1@natsu \
    --to=roman@rm.pp.ru \
    --cc=bernd.schubert@fastmail.fm \
    --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.