From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Neal Becker <ndbecker2@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: [newb] move /home to subvolume
Date: Mon, 01 Jun 2015 10:09:30 -0400 [thread overview]
Message-ID: <556C679A.4050000@gmail.com> (raw)
In-Reply-To: <mkhl70$fnu$1@ger.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On 2015-06-01 09:03, Neal Becker wrote:
> So I think what I need to do is:
>
> 1. boot off some rescue media
In theory, you may be able to boot do the equivalent of this from single
user mode or by logging in as root, although it may be safer to do it
from rescue media (just make sure the rescue media is relatively up to
date).
> 2. mount the target btrfs volume (e.g., /mnt/sysimage/root)
> 3. mv exising home (mv /mnt/sysimage/home /mnt/sysimage/oldhome)
> 4. create new subvolume (btrfs subvolume create /mnt/sysimage/home)
> 5. move all the files from /mnt/sysimage/oldhome /mnt/sysimage/home - not
> sure easiest way to do this step
I would use either rsync (if you have a lot of free space available on
the volume) or 'cp -va --reflink=always'.
> 6. edit /mnt/sysimage/etc/fstab to mount new /home
>
> I have another machine, setup more or less this way:
> UUID=7246327b-1905-4fe2-9b6b-b9376017264f / btrfs
> subvolid=5,subvol=root00 0 0
> UUID=2c04be93-34c1-4016-ba41-60fd9fd90616 /boot ext4
> defaults 1 2
> UUID=7246327b-1905-4fe2-9b6b-b9376017264f /home btrfs
> subvol=home 0 0
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]
next prev parent reply other threads:[~2015-06-01 14:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 12:36 [newb] move /home to subvolume Neal Becker
2015-06-01 12:57 ` Vytautas D
2015-06-01 13:03 ` Neal Becker
2015-06-01 13:57 ` Justus Seifert
2015-06-01 14:09 ` Austin S Hemmelgarn [this message]
2015-06-01 18:18 ` Chris Murphy
[not found] ` <CAG3t+pEHqATjGFUQrLn__O5-ByW4oX6MWjQiYh9GpgfqdKKiyg@mail.gmail.com>
2015-06-01 19:13 ` Chris Murphy
2015-06-01 23:03 ` Neal Becker
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=556C679A.4050000@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=ndbecker2@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.