Re: RBD layering design draft

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

 



> On 06/15/2012 03:48 PM, Josh Durgin wrote:

> > Then you can perform the clone:
> >     $ rbd clone --parent pool/parent@snap pool2/child1
> 
> Based on my comments above, if the parent had not been "preserved"
> it would automatically be at this point, by virtue of the fact it
> has a clone associated with it.
> 
> Since there is always exactly one parent and one child, I'd say
> drop the "--parent" and just have the parent and child be
> defined by their position.  If the parent could be optionally
> skipped for some reason, then make it be the second one.

I think that would be a very bad idea. clone <source> <target> would be a good 
idea; nearly all similar commandline utilities (cp, mv, ln) work like that. 
clone <target> <source> would be counterintuitive and probably lead to 
otherwise avoidable mistakes.

        Guido
--
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