From: Yuri D'Elia <wavexx@users.sf.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Question on subvolumes and mount options
Date: Mon, 14 Feb 2011 12:40:33 +0100 [thread overview]
Message-ID: <20110214124033.13993f8d.wavexx@users.sf.net> (raw)
In-Reply-To: 20110213191820.GA6321@carfax.org.uk
On Sun, 13 Feb 2011 19:18:20 +0000
Hugo Mills <hugo-lkml@carfax.org.uk> wrote:
> Yes, it's the same piece of storage, just appearing at more than
> one point in your overall filesystem. Similar to the way that bind
> mounts work.
I've noticed that I can also rename subvolumes as well using mv(1).
Can I move/re-arrange subvolumes between them simply using mv?
Does a move between subvolumes involve a copy?
> > So you would recommend creating both /root and /home subvolumes, to be
> > mounted separately, or create /root and /root/home subvolumes?
>
> The former.
Thanks. I can see why this is clearly more flexible in the long term.
> > What if I remount the /home subvol into /home2. What happens when I
> > touch a file through /home (nodatasum) and what happens when I use
> > /home2 - since both are available at the same time?
>
> They'll stay in sync with respect to the files written to either
> one. I'm not sure what the behaviour of nodatasum is with different
> mounts of the same subvolume.
Can we get an exact answer/behavior for that? :)
I mean, can I mount two different subvolumes in the same file system with different flags (such as ssd, nodatasum, compress)?
prev parent reply other threads:[~2011-02-14 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-13 16:46 Question on subvolumes and mount options Yuri D'Elia
2011-02-13 17:30 ` Hugo Mills
2011-02-13 17:49 ` Yuri D'Elia
2011-02-13 19:18 ` Hugo Mills
2011-02-14 11:40 ` Yuri D'Elia [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=20110214124033.13993f8d.wavexx@users.sf.net \
--to=wavexx@users.sf.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).