It's a bit different with rbd, as there's no current dir, but I do
tend to agree that like every other place pool defaults, which means
'rbd' literally is more correct. See my RFC from today:
RFC: incompatible change to rbd tool behavior on copy
On 11/15/2012 08:43 AM, Deb Barba wrote:
On Thu, Nov 15, 2012 at 8:43 PM, Deb Barba deb.ba...@inktank.com wrote:
This is not common UNIX/posix behavior.
if you just give the source a file name, it should assume . (current
directory) as it's location, not whatever path you started from.
I would expect most UNIX users would be losing
On 11/12/2012 02:47 PM, Josh Durgin wrote:
On 11/12/2012 08:30 AM, Andrey Korolyov wrote:
Hi,
For this version, rbd cp assumes that destination pool is the same as
source, not 'rbd', if pool in the destination path is omitted.
rbd cp install/img testimg
rbd ls install
img testimg
Is this
On Thu, Nov 15, 2012 at 4:56 AM, Dan Mick dan.m...@inktank.com wrote:
On 11/12/2012 02:47 PM, Josh Durgin wrote:
On 11/12/2012 08:30 AM, Andrey Korolyov wrote:
Hi,
For this version, rbd cp assumes that destination pool is the same as
source, not 'rbd', if pool in the destination path is
Hi,
For this version, rbd cp assumes that destination pool is the same as
source, not 'rbd', if pool in the destination path is omitted.
rbd cp install/img testimg
rbd ls install
img testimg
Is this change permanent?
Thanks!
--
To unsubscribe from this list: send the line unsubscribe
On 11/12/2012 08:30 AM, Andrey Korolyov wrote:
Hi,
For this version, rbd cp assumes that destination pool is the same as
source, not 'rbd', if pool in the destination path is omitted.
rbd cp install/img testimg
rbd ls install
img testimg
Is this change permanent?
Thanks!
This is a
