linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Moving top level to a subvolume
Date: Tue, 12 Jun 2012 01:53:23 +0000 (UTC)	[thread overview]
Message-ID: <pan.2012.06.12.01.53.23@cox.net> (raw)
In-Reply-To: 1339183466.55421.YahooMailNeo@web160803.mail.bf1.yahoo.com

Matthew Hawn posted on Fri, 08 Jun 2012 12:24:26 -0700 as excerpted:

> I just converted my root filesystem to btrfs with btrfs-convert. 
> However,
> since I am running Ubuntu, I would like to have the same subvolume
> structure as a default install,. How do I move the top-level subvolume
> (where all my files currently are) to another subvolume?

(Replied to list and to you, in case you're not subscribed.)

Arne answered your question, but just let me add a caution.

We get a lot of folks on this list who somehow miss the kernel warning, 
and the wiki warning, and the general community knowledge, that btrfs is 
still marked experimental and is still under heavy development.  If 
something goes wrong, as it often has for these folks when they post 
here...

So just be aware of that and be sure that if you're going to run it, you 
keep backups on something other than btrfs just in case, and that you 
keep them relatively current (depending on how much data from your btrfs 
systems you're willing to lose if it dies).

Also, it's worthwhile to keep up with this list to see current 
developments and bugs, to run a current kernel, generally meaning latest 
Linus release either stable or rc, and if you've not read up on the wiki, 
read up on btrfs there, too.

https://btrfs.wiki.kernel.org/

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  parent reply	other threads:[~2012-06-12  1:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 19:24 Moving top level to a subvolume Matthew Hawn
2012-06-08 19:40 ` Arne Jansen
2012-06-13  7:04   ` C Anthony Risinger
2012-06-13  7:21     ` Arne Jansen
2012-06-13  9:44       ` C Anthony Risinger
2012-06-13  9:57         ` Fajar A. Nugraha
2012-06-13 16:20       ` Goffredo Baroncelli
2012-06-12  1:53 ` Duncan [this message]
2012-06-12 14:52   ` Randy Barlow
2012-06-12 15:12     ` Michael
2012-06-13  1:49     ` Fajar A. Nugraha
2012-06-13  7:23       ` Duncan
2012-06-13  9:08         ` Fajar A. Nugraha
2012-06-13 17:17           ` Duncan

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=pan.2012.06.12.01.53.23@cox.net \
    --to=1i5t5.duncan@cox.net \
    --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).