CEPH filesystem development
 help / color / mirror / Atom feed
From: Josh Durgin <jdurgin@redhat.com>
To: "Xue, Chendi" <chendi.xue@intel.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	Andrew Shewmaker <agshew@gmail.com>
Subject: Re: Checking on wip-blkin branch
Date: Tue, 16 Jun 2015 11:20:24 -0700	[thread overview]
Message-ID: <558068E8.3050305@redhat.com> (raw)
In-Reply-To: <5580594D.8040809@redhat.com>

On 06/16/2015 10:13 AM, Josh Durgin wrote:
> On 06/16/2015 12:02 AM, Xue, Chendi wrote:
>> HI, Josh and Andrew
>>
>> I just rebase the wip-blkin branch to 9.0.1, and did a rados bench
>> test on that
>>
>> https://github.com/ceph/ceph/pull/4963
>
> Thanks! Reset the branch in ceph.git.
>
>> Lttng result is collected successfully
>>
>> Considering on rados testsuits failing issues, I don't have a test
>> environment, any suggests?
>
> You should be able to reproduce the failures without teuthology. Try
> running these scripts from the ceph tree with
>
> ms inject socket failures = 5000
>
> in the [global] section of ceph.conf:
>
> qa/workunits/rados/test.sh
> qa/workunits/rados/test_pool_quota.sh
> qa/workunits/rados/cls.sh

Whoops, there's no cls.sh. I meant all the scripts in qa/workunits/cls/

>
> These resulted in osd crashes in the last rados suite run linked
> earlier in the thread.
>
> Josh
>
>> Best Regards,
>> -Chendi
>>
>> -----Original Message-----
>> From: Josh Durgin [mailto:jdurgin@redhat.com]
>> Sent: Tuesday, June 9, 2015 10:45 PM
>> To: Xue, Chendi; ceph-devel@vger.kernel.org; Andrew Shewmaker
>> Subject: Re: Checking on wip-blkin branch
>>
>> Hi Chendi,
>>
>> On 06/09/2015 04:59 AM, Xue, Chendi wrote:
>>> Hi, Josh and Andrew
>>>
>>> Today, I applied wip-blkin branch to my 4 nodes ceph setup, and
>>> created zipkin-based lttng results successfully.
>>>
>>> Since we wanna using this latency analyzing methodology on further
>>> release or on keyvalue store and newstore.
>>> I am wondering what is the gap to merge blkin into master? Can I help
>>> to rebase to master, so we can merge this branch?
>>
>> That'd be great! Andrew and I simply haven't had time to finish fixing
>> up the remaining issues. Running it through a rados suite showed some
>> more changes were necessary to handle more complicated osd usage -
>> you'll see several osd crashes in this rados suite run [1].
>>
>> The code was looking fine to me, it just needs rebasing and debugging
>> so it can pass the rados test suite.
>>
>> Thanks!
>> Josh
>>
>> [1]
>> http://pulpito.ceph.com/joshd-2015-03-25_17:29:16-rados-wip-blkin---blkin-multi/
>>
>> --
>> 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
>>
>
> --
> 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:[~2015-06-16 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 11:59 Checking on wip-blkin branch Xue, Chendi
2015-06-09 14:44 ` Josh Durgin
2015-06-16  7:02   ` Xue, Chendi
2015-06-16 17:13     ` Josh Durgin
2015-06-16 18:20       ` 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=558068E8.3050305@redhat.com \
    --to=jdurgin@redhat.com \
    --cc=agshew@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chendi.xue@intel.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