linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Stubbs <andrew.stubbs@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: How to merge two partitions?
Date: Thu, 01 Aug 2013 13:14:39 +0100	[thread overview]
Message-ID: <51FA512F.5040507@gmail.com> (raw)
In-Reply-To: <20130801110849.GZ20517@carfax.org.uk>

On 01/08/13 12:08, Hugo Mills wrote:
>> I thought of using "btrfs device add" and just living with the
>> untidy underlying devices, but an experiment with loopback
>> filesystems shows that any data on the new device is silently
>> obliterated (it might be nice if the docs mentioned this!)
>
>     You would expect data in a different filesystem format to be
> integrated into an existing set of data structures? That would be...
> magic. :)

No, this was merging two btrfs filesystem of the same format. I hoped 
that, somehow, it would just add it into the tree, perhaps as another 
subvolume. Maybe even it might not show up in the overall volume, but 
could still be mounted from the partition volume. It's all about trees, 
right?!

Anyway, what's confused me is that one of the tutorials I found says 
that you should run mkfs on the new device before adding it, but 
experimentation shows that's just not necessary. The bogus instructions 
led me to believe that the contents of the new device was significant, 
somehow.

It would be nice if "man btrfs" had a big warning that the added device 
will get wiped, effectively.

>> Is there a cunning btrfs trick to do this? Can a btrfs filesystem be
>> extended "backwards", if you see what I mean?
>
>     No, using gparted to move it backwards into the free space is your
> best option here.

OK, thanks.

Andrew

      reply	other threads:[~2013-08-01 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01 10:53 How to merge two partitions? Andrew Stubbs
2013-08-01 11:08 ` Hugo Mills
2013-08-01 12:14   ` Andrew Stubbs [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=51FA512F.5040507@gmail.com \
    --to=andrew.stubbs@gmail.com \
    --cc=hugo@carfax.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).