public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Michel Alexandre Salim <michael.silvanus@gmail.com>
Cc: linux-btrfs list <linux-btrfs@vger.kernel.org>
Subject: Re: Separate mount options for subvolumes?
Date: Tue, 15 Sep 2009 09:44:43 -0400	[thread overview]
Message-ID: <20090915134443.GV8839@think> (raw)
In-Reply-To: <615c05430909141255s614702deu44e42bbb7f7cd169@mail.gmail.com>

On Mon, Sep 14, 2009 at 03:55:39PM -0400, Michel Alexandre Salim wrote:
> Hello,
> 
> It is my understanding that currently, the only difference between
> subvolumes and snapshots are that snapshots share a root with an
> existing tree, while subvolumes start off empty.
> 
> There is an interesting use case difference, though: because a
> subvolume by definition cannot share data with other subvolumes, that
> frees it up to being mounted with different options (e.g. nodatasum,
> nodatacow).
> 
> The reason I'm wondering is that I just switched my home directory to
> btrfs, and one of my machine is often used for rebuilding RPMs (for
> initial testing, before getting it built on a build server). The data
> is never kept for a long time, and so checksumming and COW would just
> slow things down.
> 
> Would this be possible, and if so, is it planned for implementation by 1.0?

It would be possible, and long term we plan on storing a number of
options directly in the root so that you don't have to keep doing mount
-o foo.

-chris

      reply	other threads:[~2009-09-15 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 19:55 Separate mount options for subvolumes? Michel Alexandre Salim
2009-09-15 13:44 ` Chris Mason [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=20090915134443.GV8839@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=michael.silvanus@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