From: Goswin von Brederlow <goswin-v-b@web.de>
To: Neil Brown <neilb@suse.de>
Cc: Carlos Carvalho <carlos@fisica.ufpr.br>, linux-raid@vger.kernel.org
Subject: Re: Write intent bitmaps
Date: Fri, 19 Jun 2009 17:01:31 +0200 [thread overview]
Message-ID: <87ab44mfn8.fsf@frosties.localdomain> (raw)
In-Reply-To: <19002.62697.475588.28776@notabene.brown> (Neil Brown's message of "Fri, 19 Jun 2009 12:16:09 +1000")
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?
MfG
Goswin
next prev parent reply other threads:[~2009-06-19 15:01 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 [this message]
2009-06-20 8:14 ` NeilBrown
2009-06-20 9:52 ` Goswin von Brederlow
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=87ab44mfn8.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).