public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michel Alexandre Salim <michael.silvanus@gmail.com>
To: linux-btrfs list <linux-btrfs@vger.kernel.org>
Subject: Separate mount options for subvolumes?
Date: Mon, 14 Sep 2009 15:55:39 -0400	[thread overview]
Message-ID: <615c05430909141255s614702deu44e42bbb7f7cd169@mail.gmail.com> (raw)

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?

Thanks,

-- 
Michel Alexandre Salim

             reply	other threads:[~2009-09-14 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 19:55 Michel Alexandre Salim [this message]
2009-09-15 13:44 ` Separate mount options for subvolumes? Chris Mason

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=615c05430909141255s614702deu44e42bbb7f7cd169@mail.gmail.com \
    --to=michael.silvanus@gmail.com \
    --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