All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Jason Dillaman <dillaman@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
	Josh Durgin <jdurgin@redhat.com>
Subject: Re: long running workloads/rbd_fsx_cache_writeback.yaml on hammer
Date: Fri, 08 May 2015 17:13:36 +0200	[thread overview]
Message-ID: <554CD2A0.3040101@dachary.org> (raw)
In-Reply-To: <209815215.14051495.1431097392961.JavaMail.zimbra@redhat.com>

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



On 08/05/2015 17:03, Jason Dillaman wrote:
> Since it sounds like the next hammer release is more or less ready, my vote would be that the fix can wait until the next release.  Since it will only occur if the new exclusive lock feature is enabled (disabled on images by default) and the connection between librbd and the OSD is reset with writeback data waiting in the cache, it sounds like a rare enough issue.
> 
> Final decision rests w/ Josh.

Ok :-) Would you be so kind as to point me to the corresponding issue in the tracker for reference ?

-- 
Loïc Dachary, Artisan Logiciel Libre


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

  reply	other threads:[~2015-05-08 15:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  9:07 long running workloads/rbd_fsx_cache_writeback.yaml on hammer Loic Dachary
2015-05-08 12:36 ` Jason Dillaman
2015-05-08 14:34   ` Loic Dachary
2015-05-08 15:03     ` Jason Dillaman
2015-05-08 15:13       ` Loic Dachary [this message]
2015-05-08 16:07         ` Josh Durgin
2015-05-08 16:57           ` Yuri Weinstein

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=554CD2A0.3040101@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.