linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: NeilBrown <neilb@suse.de>
Cc: Goswin von Brederlow <goswin-v-b@web.de>,
	Carlos Carvalho <carlos@fisica.ufpr.br>,
	linux-raid@vger.kernel.org
Subject: Re: Write intent bitmaps
Date: Sat, 20 Jun 2009 11:52:30 +0200	[thread overview]
Message-ID: <87ws77cjvl.fsf@frosties.localdomain> (raw)
In-Reply-To: <8980e5d278405d56e8d5c128d17fe0cf.squirrel@neil.brown.name> (NeilBrown's message of "Sat, 20 Jun 2009 18:14:21 +1000 (EST)")

"NeilBrown" <neilb@suse.de> writes:

> On Sat, June 20, 2009 1:01 am, Goswin von Brederlow wrote:
>> Neil Brown <neilb@suse.de> writes:
>>
>>> On Monday June 8, carlos@fisica.ufpr.br wrote:
>>>>  >If so, would ext2 probably be the best choice?
>>>>
>>>> That's what the man page says. I find it strange since if it's a file
>>>> the filesystem shouldn't matter. Neil?
>>>
>>> The way that md writes to the bitmap file is not entirely portable
>>> across different filesystems.  As the man page say,  it is known to
>>> work for ext2 and ext3.  Either is a fine choice.
>>> A new filesystem interface is being introduced in 2.6.31 as part of
>>> the swap-over-NFS work.  I might end up using that to write to bitmap
>>> files, as it has the right characteristics.  But that is very much in
>>> the future.
>>>
>>> NeilBrown
>>
>> How about support to write to a device instead of a file?
>
> One of my next little projects is to rationalise the bitmap support
> and make it more generic - currently you cannot use bitmaps with
> externally managed metadata because there is no way to say where
> it should go.
> I don't know yet how that will end up working, but it is entirely possible
> that it will generalise to allows the bitmap to be written to an
> arbitrary device.
>
> However, as bitmaps are typically quite small (a few megabytes at
> most, typically tens of kilobytes) it seems clumsy to create a
> partition just for a bitmap..
>
> NeilBrown

lvcreate --extents 1 ...

Ideal would be if one could put multiple bitmaps on the same
device. But then again that is what an FS allows.

MfG
        Goswin


  reply	other threads:[~2009-06-20  9:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  2:10 Write intent bitmaps Leslie Rhorer
2009-06-08 13:51 ` Carlos Carvalho
2009-06-18  8:17   ` Goswin von Brederlow
2009-06-19  2:24     ` Neil Brown
2009-06-19  5:21       ` Goswin von Brederlow
2009-06-19  2:16   ` Neil Brown
2009-06-19 15:01     ` Goswin von Brederlow
2009-06-20  8:14       ` NeilBrown
2009-06-20  9:52         ` Goswin von Brederlow [this message]
2009-06-21 18:06     ` Bill Davidsen
2009-06-28 18:14     ` Leslie Rhorer
2009-06-29 10:01       ` Goswin von Brederlow
  -- strict thread matches above, loose matches on Subject: below --
2009-08-23  8:16 RAID 5 recovery to not degrade device on bad block Anshuman Aggarwal
2009-08-24 12:54 ` Goswin von Brederlow
2009-08-24 14:39   ` Write intent bitmaps Simon Jackson
     [not found]     ` <ABFC24E4C13D81489F7F624E14891C860D1F15EF@uk-ex-mbx1.terastack.bluearc .com>
2009-08-24 20:25       ` NeilBrown
2009-09-02 16:10         ` Bill Davidsen
2009-09-02 16:28           ` Paul Clements
2009-09-02 17:36             ` Ryan Wagoner

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=87ws77cjvl.fsf@frosties.localdomain \
    --to=goswin-v-b@web.de \
    --cc=carlos@fisica.ufpr.br \
    --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).