linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: "Mathias Burén" <mathias.buren@gmail.com>
Cc: NeilBrown <neilb@suse.de>, Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: External bitmap, questions
Date: Sat, 19 Feb 2011 17:14:37 +0500	[thread overview]
Message-ID: <20110219171437.3a6200e6@natsu> (raw)
In-Reply-To: <AANLkTimpQ2=EM97ELX3z4c=Yf6gDp=Ekdn6m+ws6O8rm@mail.gmail.com>

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

On Sat, 19 Feb 2011 04:55:32 +0000
Mathias Burén <mathias.buren@gmail.com> wrote:

> > External bitmaps use 'BMAP' to find where the file lives on the device and
> > then writes directly to the device - not through the filesystem.
> >
> > So as long as there is no tail-packing to block migration happening it
> > should work fine.
> >
> > I haven't looked inside ext4 but I am fairly confident that external
> > bitmaps will work properly.
> >
> > NeilBrown
> >
> >
> 
> Thanks, Neil. Are there any differences between using an internal or
> external bitmap? Also, does one need a bitmap at all when not planning
> to "mess" with the array? (does it provide any other purpose?)

I have successfully stored an external bitmap on XFS for a brief time.
However it proved difficult to ensure that the device storing the bitmap is
mounted, accessible and writable prior to boot scripts attempting to run the md
arrays, so since then I just switched to an internal bitmap. The negative
performance it had can be minimized to almost zero by using a larger bitmap
chunk size.

-- 
With respect,
Roman

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

  parent reply	other threads:[~2011-02-19 12:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-19  0:47 External bitmap, questions Mathias Burén
2011-02-19  4:49 ` NeilBrown
2011-02-19  4:55   ` Mathias Burén
2011-02-19  5:30     ` NeilBrown
2011-02-19  5:42       ` Mathias Burén
2011-02-19 12:14     ` Roman Mamedov [this message]
2011-02-19 12:20       ` Mathias Burén
2011-02-19 12:32         ` Roman Mamedov

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=20110219171437.3a6200e6@natsu \
    --to=rm@romanrm.ru \
    --cc=linux-raid@vger.kernel.org \
    --cc=mathias.buren@gmail.com \
    --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).