CEPH filesystem development
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@inktank.com>
Cc: Yehuda Sadeh <yehuda@inktank.com>,
	Josh Durgin <josh.durgin@inktank.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: RBD layering design draft
Date: Sun, 17 Jun 2012 15:42:59 +0200	[thread overview]
Message-ID: <4FDDDEE3.8020405@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1206160808050.1862@cobra.newdream.net>

Hi,
what's up locked, unlocked, unlocking?

-martin

Am 16.06.2012 17:11, schrieb Sage Weil:
> On Fri, 15 Jun 2012, Yehuda Sadeh wrote:
>> On Fri, Jun 15, 2012 at 5:46 PM, Sage Weil<sage@inktank.com>  wrote:
>>> Looks good!  Couple small things:
>>>
>>>>      $ rbd unpreserve pool/image@snap
>>>
>>> Is 'preserve' and 'unpreserve' the verbiage we want to use here?  Not sure
>>> I have a better suggestion, but preserve is unusual.
>>>
>>
>> freeze, thaw/unfreeze?
>
> Freeze/thaw usually mean something like quiesce I/O or read-only, usually
> temporarily.  What we actaully mean is "you can't delete this".  Maybe
> pin/unpin?  preserve/unpreserve may be fine, too!
>
> sage

  reply	other threads:[~2012-06-17 13:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-15 20:48 RBD layering design draft Josh Durgin
2012-06-16  0:46 ` Sage Weil
2012-06-16  2:00   ` Yehuda Sadeh
2012-06-16 15:11     ` Sage Weil
2012-06-17 13:42       ` Martin Mailand [this message]
2012-06-18 18:04         ` Gregory Farnum
2012-06-18 16:25   ` Tommi Virtanen
2012-06-18 23:10     ` Dan Mick
2012-06-18 17:00 ` Tommi Virtanen
2012-06-18 17:14   ` Josh Durgin
2012-06-18 18:01     ` Sage Weil
2012-06-18 23:07       ` Dan Mick
2012-06-22  2:02         ` Alex Elsayed
2012-06-22 14:41           ` Guido Winkelmann
2012-06-22 14:36   ` Guido Winkelmann
2012-06-22 16:00     ` Tommi Virtanen
2012-06-21 21:51 ` Alex Elder
2012-06-22 14:37   ` Guido Winkelmann
2012-06-22 16:27   ` Tommi Virtanen

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=4FDDDEE3.8020405@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=josh.durgin@inktank.com \
    --cc=sage@inktank.com \
    --cc=yehuda@inktank.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