Re: RBD layering design draft

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Locking is a separate mechanism we're already working on, which will
"lock" images so that they can't accidentally be mounted at more than
one location. :)
-Greg

On Sun, Jun 17, 2012 at 6:42 AM, Martin Mailand <martin@xxxxxxxxxxxx> wrote:
> 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@xxxxxxxxxxx>  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
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux