From: Martin Mailand <martin@tuxadero.com>
To: Josh Durgin <josh.durgin@dreamhost.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: rbd snap
Date: Sat, 17 Sep 2011 18:09:55 +0200 [thread overview]
Message-ID: <4E74C653.6080404@tuxadero.com> (raw)
In-Reply-To: <4E73CC58.9070503@dreamhost.com>
Okay, with the btrfs patch and the right commandline snapshotting works
like a charm.
best regards,
martin
Josh Durgin schrieb:
> On 09/16/2011 02:32 PM, Martin Mailand wrote:
>> root@c-brick-001:~# rbd rm --snap=2011091601 test
>> *** Caught signal (Segmentation fault) **
>> in thread 0x7f203d749740
>> ceph version 0.34 (commit:2f039eeeb745622b866d80feda7afa055e15f6d6)
>> 1: rbd() [0x457062]
>> 2: (()+0xfc60) [0x7f203ccf6c60]
>> 3: (librbd::snap_set(librbd::ImageCtx*, char const*)+0x10)
>> [0x7f203d32ecd0]
>> 4: (main()+0x59f) [0x4518ff]
>> 5: (__libc_start_main()+0xff) [0x7f203b6cdeff]
>> 6: rbd() [0x44d569]
>> Segmentation fault
>
> I added a bug to the tracker for this
> (http://tracker.newdream.net/issues/1545). It shouldn't crash the way
> you ran it, but if you're trying to remove a snapshot you need to use
> the 'snap rm' command, i.e.:
> $ rbd snap rm --snap=2011091601 test
> --
> 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:[~2011-09-17 16:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 14:45 rbd snap Martin Mailand
2011-09-16 16:30 ` Sage Weil
2011-09-16 21:32 ` Martin Mailand
2011-09-16 22:23 ` Josh Durgin
2011-09-16 22:36 ` Martin Mailand
2011-09-17 16:09 ` Martin Mailand [this message]
2011-09-23 18:08 ` Martin Mailand
2011-09-23 18:21 ` Sage Weil
2011-09-23 18:48 ` Martin Mailand
2011-09-23 18:52 ` Sage Weil
2011-09-23 18:25 ` Josh Durgin
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=4E74C653.6080404@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@dreamhost.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