From: Christoph Hellwig <hch@infradead.org>
To: linux-raid@vger.kernel.org
Subject: external bitmaps on block devices?
Date: Mon, 22 Aug 2011 23:51:55 -0400 [thread overview]
Message-ID: <20110823035155.GA12299@infradead.org> (raw)
Is there any specific reason to require the external bitmap to be on
a file? Currently the code requires regular files to call bmap on them,
which is a fairly dangerous thing to start with. But why don't we just
allow using block devices to store the bitmap directly?
next reply other threads:[~2011-08-23 3:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 3:51 Christoph Hellwig [this message]
2011-08-23 4:04 ` external bitmaps on block devices? NeilBrown
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=20110823035155.GA12299@infradead.org \
--to=hch@infradead.org \
--cc=linux-raid@vger.kernel.org \
/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.