From: Josh Durgin <josh.durgin@inktank.com>
To: Dan Mick <dan.mick@inktank.com>
Cc: jie sun <0maidou0@gmail.com>, ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: some questions about rbd
Date: Tue, 23 Oct 2012 10:47:28 -0700 [thread overview]
Message-ID: <5086D830.5010505@inktank.com> (raw)
In-Reply-To: <5086386D.2030002@inktank.com>
Currently there's no way to force deletion of a RADOS object that
has watchers. Clients with an rbd image open watch the header
object, hence the error you saw.
There's a feature request open for this at the RADOS level:
http://www.tracker.newdream.net/issues/2339
I'm curious about why you want to delete an image even
if a vm is still using it. What's the context in which this
becomes necessary?
Josh
On 10/22/2012 11:25 PM, Dan Mick wrote:
> I don't think we support that; I'm not sure how hard it would be.
> Somehow we'd have to keep knowledge of the open image handle around to
> fail further I/O requests, it seems. Josh?
>
> On 10/22/2012 10:44 PM, jie sun wrote:
>> Yes. I want to delete the image by force, even the vm is still using it.
>>
>> 2012/10/23 Dan Mick <dan.mick@inktank.com>:
>>>
>>>
>>> On 10/22/2012 08:10 PM, jie sun wrote:
>>>>
>>>> Hi,
>>>>
>>>> I create a image and map it to a virtual machine,and then mkfs and
>>>> mount
>>>> it.
>>>>
>>>> I want to remove the image from mon server forcely, but it says
>>>> "Removing image: 99% complete...failed.
>>>> delete error: image still has watchers
>>>> This means the image is still open or the client using it crashed.
>>>> Try again after closing/unmapping it or waiting 30s for the crashed
>>>> client to timeout."
>>>>
>>>> I want to know is there any other way to remove it by force?
>>>
>>>
>>> Are you saying the vm still has the device open and is trying to use it?
>>> But even so, you want the image to be deleted?
>>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-10-23 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB6Jr7QLS1=G0vPavT70knKUteDczF4yho1Bha_Tgsv1tsXusA@mail.gmail.com>
2012-10-23 3:10 ` some questions about rbd jie sun
2012-10-23 4:21 ` Dan Mick
[not found] ` <CAB6Jr7QYrugfTModh85JFtkga2zPN_6tKJ1cSMA78+H85ksbcw@mail.gmail.com>
2012-10-23 6:25 ` Dan Mick
2012-10-23 17:47 ` Josh Durgin [this message]
2012-10-25 6:25 ` jie sun
2012-10-25 7:27 ` Wido den Hollander
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=5086D830.5010505@inktank.com \
--to=josh.durgin@inktank.com \
--cc=0maidou0@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=dan.mick@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