All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@dreamhost.com>
To: Simon Tian <aixt2006@gmail.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: rbd create error with 0.26
Date: Fri, 12 Aug 2011 11:18:08 -0700	[thread overview]
Message-ID: <4E456E60.6090808@dreamhost.com> (raw)
In-Reply-To: <4E456936.3020800@dreamhost.com>

On 08/12/2011 10:56 AM, Josh Durgin wrote:
> (bringing back to the list)
>
> On 08/12/2011 12:33 AM, Simon Tian wrote:
>> I have done all these:
>> 1 cosd has permission to write /var/lib/ceph/tmp
>> 2 The temp partition (/var/lib/ceph/tmp) has the execution permission
>> ( no noexec mount option )
>> 3 libcls_rbd.so is found in LD_LIBRARY_PATH or in the path specified
>> in ceph.conf (osd class dir = /usr/lib64/rados-classes for distros
>> like RHEL6)
>>
>> I am testing on RHEL5.4.
>>
>> The error didn't disappear....
>
> Could you add 'debug osd = 20' to your ceph.conf, restart your osds,
> then try again? The osd log should tell us the cause of the error.
>

On further inspection, the wiki was wrong - LD_LIBRARY_PATH does not 
affect class loading. You probably just need to set 'osd class dir = 
/usr/lib64/rados-classes'.

>> 2011/8/12 Simon Tian<aixt2006@gmail.com>:
>>> # rbd create foo --size 1024
>>> 2011-08-12 10:13:13.180774 7f4c9a6656f0 librbd: failed to assign a
>>> block name for image
>>> create error: Input/output error
>>>
>>>
>>> 2011/8/11 Josh Durgin<josh.durgin@dreamhost.com>:
>>>> On Thu, 11 Aug 2011 22:49:11 +0800, Simon Tian<aixt2006@gmail.com>
>>>> wrote:
>>>>> Hi folks,
>>>>>
>>>>> This assert failure appeared in ceph-0.31 when creating a pool,
>>>>> could anyone help me?
>>>>>
>>>>> Thx
>>>>> Simon
>>>>
>>>> What's the error?
>>>>
>>>
>
> --
> 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


  reply	other threads:[~2011-08-12 18:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  2:30 rbd create error with 0.26 Simon Tian
2011-05-10  9:35 ` Yehuda Sadeh Weinraub
2011-05-10 13:39   ` Simon Tian
2011-05-10 13:59     ` Yehuda Sadeh Weinraub
2011-05-10 14:15       ` Simon Tian
2011-05-10 14:42         ` Yehuda Sadeh Weinraub
2011-05-11  1:54           ` Simon Tian
2011-05-12  0:56             ` Josh Durgin
2011-05-13  7:45           ` Simon Tian
2011-05-13 15:58             ` Sage Weil
2011-05-14  3:26               ` Simon Tian
2011-05-15  9:39               ` Simon Tian
2011-05-15  9:40                 ` Simon Tian
2011-05-15 12:57                 ` Simon Tian
2011-05-16  4:33                 ` Sage Weil
2011-05-16  6:44                   ` Simon Tian
2011-05-16 15:40                     ` Gregory Farnum
2011-05-10 14:29       ` Simon Tian
2011-05-10 11:47 ` Fyodor Ustinov
2011-05-10 13:50   ` Simon Tian
2011-08-11 14:49 ` Simon Tian
2011-08-11 15:47   ` Josh Durgin
     [not found]     ` <CAFGK4N+wDdK13o_Sy+fxRxwZ+mZT+TEUJt3+GhKW8CQRRSE7UQ@mail.gmail.com>
     [not found]       ` <CAFGK4NKoNewHP2E76EJxWBSOTPgSKf=5SemjockSGTEj+1u4hA@mail.gmail.com>
2011-08-12 17:56         ` Josh Durgin
2011-08-12 18:18           ` Josh Durgin [this message]
2011-08-15  3:15             ` Simon Tian

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=4E456E60.6090808@dreamhost.com \
    --to=josh.durgin@dreamhost.com \
    --cc=aixt2006@gmail.com \
    --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.