From: Russell Coker <russell@coker.com.au>
To: Tim Cuthbertson <ratcheer@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Managing large volumes
Date: Fri, 3 Jan 2014 12:55:43 +1100 [thread overview]
Message-ID: <201401031255.43845.russell@coker.com.au> (raw)
In-Reply-To: <CAAKzf7kB90qOG8yNuLUyfd2w61kVeeo+d+vs=ecURYqm=rjxgg@mail.gmail.com>
On Fri, 3 Jan 2014, Tim Cuthbertson <ratcheer@gmail.com> wrote:
> 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.
Why do you use RAID-0?
> 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?
A fairly standard OS install feature is to not run mkfs on a partition. So if
you had your system configured such that the current root is a subvol and that
the root of the BTRFS filesystem has no names that match a regular
installation (IE not having /usr etc) then it should just work. Even if you
use a /home subvol for the home directories that shouldn't be a real problem
as the account creation process shouldn't remove old accounts.
One other issue you may have is that you need the installer to have a new
enough kernel to support the filesystem. If you install a system from a
Debian/Wheezy CD and then upgrade it to Debian/Unstable then I think it gets
some new filesystem features that make it impossible to mount with
Debian/Wheezy. I recall having to upgrade a Debian/Wheezy system to a
Debian/Unstable kernel so it could mount a BTRFS removable device that had
been mounted on a Debian/Unstable system.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
prev parent reply other threads:[~2014-01-03 1:56 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
2014-01-03 1:55 ` Russell Coker [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=201401031255.43845.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=ratcheer@gmail.com \
/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