From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Managing large volumes
Date: Fri, 03 Jan 2014 01:48:36 +0100 [thread overview]
Message-ID: <40ehpa-sk6.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: CAAKzf7kB90qOG8yNuLUyfd2w61kVeeo+d+vs=ecURYqm=rjxgg@mail.gmail.com
Tim Cuthbertson <ratcheer@gmail.com> schrieb:
> I am a bit confused and I have probably managed to outsmart myself.
> For about 15 months, I have been running my system on a single, large
> btrfs volume. It is RAID-0 on two SATA-III HDD's for a total of 1.9
> TB. This is a home system running Siduction (Debian Sid) Linux. While
> I have root, home, and a special data directory each as separate
> subvolumes, I am beginning to wonder whether I should have made each
> of these on separate partitions and separate btrfs filesystems.
>
> Am am at a point where I would like to do a fresh install of my OS
> without losing my home and data contents. And I do not think separate
> btrfs subvolumes will help me on that. Is that correct? Is there a way
> to prevent an OS installation from formatting the /home and /data
> subvolumes while completely replacing the root subvolume? Or do I need
> to completely repartition my drives so I don't get into this
> situation, again?
How about installing into a new root subvolume? I don't know if the Debian
installer allows you to do that. But this way you could easily roll back
later, or grab config files from there, or, or... And when you are done,
simply remove the old root subvolume or deduplicate it using dedup and keep
it around for archival purposes.
The one-partition layout is probably okay, tho many installers lack native
support for it. But, at least this is how I think about it, take subvolumes
as dynamically sized partitions from your storage pool.
Just keep in mind you don't want the installer to format your btrfs. You
probably want to take a backup of your data first. It is probably possible
to bootstrap your Debian installation by first creating your new subvolume,
then mount it and use it as bootstrapped destination or chroot into it to
run the installation. You could bind-mount your data and home there so it is
visible to the installer for it to import your user id.
HTH
Kai
next prev parent reply other threads:[~2014-01-03 0:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 22:28 Managing large volumes Tim Cuthbertson
2014-01-03 0:10 ` Chris Murphy
2014-01-03 0:28 ` Duncan
2014-01-03 0:48 ` Kai Krakow [this message]
2014-01-03 1:55 ` Russell Coker
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=40ehpa-sk6.ln1@hurikhan77.spdns.de \
--to=hurikhan77+btrfs@gmail.com \
--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