linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@mikefedyk.com>
To: Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
Cc: David Arendt <admin@prnet.org>, linux-btrfs@vger.kernel.org
Subject: Re: Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots)
Date: Mon, 29 Nov 2010 13:43:22 -0800	[thread overview]
Message-ID: <AANLkTikK0OEJneHWqABnOA+c9e1-QirctS34mV0bOFCv@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=VP4jStt41sYAD=6g8FwRfGrhqZB2pGcZjNbiN@mail.gmail.com>

On Mon, Nov 29, 2010 at 1:31 PM, Andrey Kuzmin
<andrey.v.kuzmin@gmail.com> wrote:
> This may sound excessive as any new concept introduction that late in
> development, but readonly/writable snapshots could be further
> differentiated by naming the latter clones. This way end-user would
> naturally perceive snapsot as read-only PIT fs image, while clone
> would naturally refer to (writable) head fork.
>

I'm not sure we want to take all of the terminology that zfs uses as
it may also bring the percieved drawbacks as well.  Isn't there some
additional overhead for a zfs clone compared to a snapshot?  I'm not
very familiar with zfs so that's why I ask.

  reply	other threads:[~2010-11-29 21:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 20:02 Default to read-only on snapshot creation and have a flag if snapshot should be writable (was: [PATCH 0/5] btrfs: Readonly snapshots) Mike Fedyk
2010-11-29 20:41 ` David Arendt
2010-11-29 21:08   ` Mike Fedyk
2010-11-29 21:31     ` Andrey Kuzmin
2010-11-29 21:43       ` Mike Fedyk [this message]
2010-11-29 21:48         ` Andrey Kuzmin
2010-11-30  0:33           ` C Anthony Risinger
2010-11-30  2:17             ` Li Zefan
2010-11-30 12:44               ` Andrey Kuzmin

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=AANLkTikK0OEJneHWqABnOA+c9e1-QirctS34mV0bOFCv@mail.gmail.com \
    --to=mfedyk@mikefedyk.com \
    --cc=admin@prnet.org \
    --cc=andrey.v.kuzmin@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;
as well as URLs for NNTP newsgroup(s).