From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: bug in rbd rename command?
Date: Fri, 19 Apr 2013 09:28:23 +0200 [thread overview]
Message-ID: <5170F217.9020105@profihost.ag> (raw)
Hi,
if i issue rbd -p POOLNAME ... rename a b
It uses the POOL for a but not for b.
Output is then:
rbd: mv/rename across pools not supported
source pool: vmstorssd1 dest pool: rbd
Shouldn't it use the pool provided by -p for both?
Stefan
next reply other threads:[~2013-04-19 7:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 7:28 Stefan Priebe - Profihost AG [this message]
2013-04-19 20:26 ` bug in rbd rename command? Dan Mick
2013-04-19 20:29 ` Stefan Priebe
2013-04-19 20:33 ` Sage Weil
2013-04-19 20:34 ` Stefan Priebe
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=5170F217.9020105@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=ceph-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.