All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Jason Dillaman <dillaman@redhat.com>, Josh Durgin <jdurgin@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: workloads/rbd_fsx_cache_writethrough.yaml hangs on dumpling
Date: Mon, 02 Feb 2015 14:18:31 +0100	[thread overview]
Message-ID: <54CF7927.7010908@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]

Hi,

http://pulpito.ceph.com/loic-2015-01-29_15:39:38-rbd-dumpling-backports---basic-multi/730029/ hangs on dumpling and got killed after two days.

Although workloads/rbd_fsx_cache_writethrough.yaml  was running with the thrasher, it does not seem to be related to http://tracker.ceph.com/issues/10513 : it was running on a mira070 (16GB RAM) and plana78 (8GB RAM). 

I don't see anything in https://github.com/ceph/ceph-qa-suite/blob/master/tasks/rbd_fsx.py that would suggest it needs backporting a fix to the ceph-qa-suite branch of dumpling.

I browsed the commits related to RBD that are in the dumpling-backports branch ( see here for the list I used http://tracker.ceph.com/issues/10560 ). I don't see anything in the issues that need backporting to dumpling either. 

Another run of this specific test has been scheduled to check if it always happens at http://pulpito.ceph.com/loic-2015-02-02_13:58:32-rbd:thrash:workloads:rbd_fsx_cache_writethrough.yaml-dumpling-backports---basic-multi/

Does that ring a bell by any chance ?

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-02-02 13:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 13:18 Loic Dachary [this message]
2015-02-02 13:48 ` workloads/rbd_fsx_cache_writethrough.yaml hangs on dumpling Yan, Zheng
2015-02-02 15:00   ` Loic Dachary
2015-02-02 16:46     ` Gregory Farnum
2015-02-02 17:10       ` Loic Dachary

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=54CF7927.7010908@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=dillaman@redhat.com \
    --cc=jdurgin@redhat.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 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.