From: Chris Mason <chris.mason@oracle.com>
To: Goffredo Baroncelli <kreijack@inwind.it>
Cc: "Billy Crook" <billycrook@gmail.com>,
"Ernst Sjöstrand" <ernstp@gmail.com>,
"Jordan Windsor" <jordanw2@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Grow btrfs partition & filesystem backwards
Date: Wed, 9 Nov 2011 14:26:56 -0500 [thread overview]
Message-ID: <20111109192656.GR9368@shiny> (raw)
In-Reply-To: <2286851.zJGgl5jPAW@venice>
On Wed, Nov 09, 2011 at 07:58:44PM +0100, Goffredo Baroncelli wrote:
> On Wednesday, 09 November, 2011 08:36:24 Chris Mason wrote:
> > The only choice for an online operation is to make a new partition in
> > front of the old one and just add that as a second disk in btrfs.
> >
> > The slow method of shifting the bytes down is probably a better long
> > term choice.
> >
> > -chris
>
> Hi Chris,
>
> does the chunk tree be able to map the sectors "before" ? If so we should only
> "shift down" the map logical->physical in the chunk tree/device tree.
>
> The only exception should be the superblock which has to be moved.
>
> At the mount time we should pass a parameter which set how the data should be
> moved backward. Then the kernel remap the chunk tree/device tree.
>
> I don't know if the gains is greater than the work, but from a theoretical
> point of view, it should be doable..
Agreed, if we wanted to sit down and write a tool, it wouldn't be that
complex. The only tricky part is maintaining alignment and position of
the super blocks.
-chris
prev parent reply other threads:[~2011-11-09 19:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 4:23 Grow btrfs partition & filesystem backwards Jordan Windsor
2011-11-09 8:50 ` Ernst Sjöstrand
2011-11-09 12:40 ` Billy Crook
2011-11-09 13:36 ` Chris Mason
2011-11-09 18:58 ` Goffredo Baroncelli
2011-11-09 19:26 ` Chris Mason [this message]
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=20111109192656.GR9368@shiny \
--to=chris.mason@oracle.com \
--cc=billycrook@gmail.com \
--cc=ernstp@gmail.com \
--cc=jordanw2@gmail.com \
--cc=kreijack@inwind.it \
--cc=linux-btrfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox