From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: In-place conversion and alignment needs
Date: Mon, 18 Mar 2013 21:20:21 +0000 (UTC) [thread overview]
Message-ID: <ki80el$q52$1@ger.gmane.org> (raw)
Hello,
I've started using bcache after writing a tool to convert existing
partitions and logical volumes into bcache volumes, available here:
<https://github.com/g2p/blocks>
I'm very happy with the performance, but there is a fundamental problem
with the conversion, which has to do with the current fixed offset from
the backing device's bcache superblock to the start of the filesystem
data.
With a plain partition this means the conversion creates an unaligned
partition, which will break the lesser-common-denominator approach tools
like parted use to determine partition alignment; it could complicate
things down the line but it's workable.
With LVM the conversion has to shift the data by exactly 4MB, which is
not possible with the current bcache. I'm working around it by putting a
small partition table between the LV and the bcache device, but that
brings some extra complexity; resizing the LV involves resizing the
partition table, which is the sort of annoyance LVM is supposed to get
rid of in the first place.
In the interest of making bcache easier to install and use, I'd like to
plead for a customisable data offset. The superblock format appears to
be extensible thanks to the version field, most of the pieces are there
for a safe transition. There is even a commented out implementation in
the userland tools, presumably Kent already has thought of it?
reply other threads:[~2013-03-18 21:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='ki80el$q52$1@ger.gmane.org' \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox