From: Josh Durgin <josh.durgin@inktank.com>
To: Matthew Anderson <matthewa@base3.com.au>
Cc: "'ceph-devel@vger.kernel.org'" <ceph-devel@vger.kernel.org>
Subject: Re: VM Corruption on 0.54 when 'client cache = false'
Date: Wed, 05 Dec 2012 13:25:19 -0800 [thread overview]
Message-ID: <50BFBBBF.6090600@inktank.com> (raw)
In-Reply-To: <38A500831D3DE24B90BD200D6C8701351BAE4F38@Exchange2010-2.corit.local>
On 12/05/2012 05:51 AM, Matthew Anderson wrote:
> Thanks for getting back to me Josh.
>
> I've updated to the new 0.55 release and I haven't been able to reproduce the problem. I have the feeling I may be to blame for the problem as when I updated to 0.55 qemu-img segfaulted with a librbd error because there was an old version of the librbd library in another path (which I think was from 0.54). Once I cleaned everything up it worked fine.
Good to hear.
> One thing I didn't notice about the 0.55 release is that 'ceph osd create' no longer accepts arguments and gives '(22) Invalid argument' if you try to specify an OSD number. Running the command without an argument correctly creates an OSD with the next free osd number. I wasn't sure if this was a bug or that the command has changed for 0.55+ and the documentation hasn't been updated yet (Add/Remove OSD's page in the wiki refernces the command with arguments).
This actually changed from accepting an osd id to a uuid back in 0.47,
but 0.55 is the first version to reject a non-uuid. The docs were
updated by 36e7b077a77fa0a6c87289f400391c85dcdb1d42, but seem to
have been accidentally reverted during a reorganization. This is
fixed again now.
This thread has the rationale for the change from id to uuid:
http://permalink.gmane.org/gmane.comp.file-systems.ceph.devel/8296
Josh
prev parent reply other threads:[~2012-12-05 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 2:18 VM Corruption on 0.54 when 'client cache = false' Matthew Anderson
2012-12-03 5:01 ` Yehuda Sadeh
2012-12-03 10:00 ` Josh Durgin
2012-12-05 13:51 ` Matthew Anderson
2012-12-05 21:25 ` Josh Durgin [this message]
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=50BFBBBF.6090600@inktank.com \
--to=josh.durgin@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=matthewa@base3.com.au \
/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.