From: Josh Durgin <josh.durgin@inktank.com>
To: ceph-devel@vger.kernel.org
Subject: Re: [PATCH 0/3] block I/O when cluster is full
Date: Thu, 05 Dec 2013 17:47:21 -0800 [thread overview]
Message-ID: <52A12CA9.3020008@inktank.com> (raw)
In-Reply-To: <1386112373-25610-1-git-send-email-josh.durgin@inktank.com>
On 12/03/2013 03:12 PM, Josh Durgin wrote:
> These patches allow rbd to block writes instead of returning errors
> when OSDs are full enough that the FULL flag is set in the osd map.
> This avoids filesystems on top of rbd getting confused by transient
> EIOs if the cluster oscillates between full and non-full.
>
> These are also available in the wip-full branch of ceph-client.git.
>
> Josh Durgin (3):
> libceph: block I/O when PAUSE or FULL osd map flags are set
> libceph: add an option to configure client behavior when osds are
> full
> rbd: document rbd-specific options
Due to a race condition between clients and osds in handling maps
marked FULL, it's not feasible to offer the 'error' option, so patches
2 and 3 can be ignored.
http://tracker.ceph.com/issues/6938
next prev parent reply other threads:[~2013-12-06 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 23:12 [PATCH 0/3] block I/O when cluster is full Josh Durgin
2013-12-03 23:12 ` [PATCH 1/3] libceph: block I/O when PAUSE or FULL osd map flags are set Josh Durgin
2013-12-07 3:02 ` Li Wang
2013-12-09 23:52 ` Josh Durgin
2013-12-03 23:12 ` [PATCH 2/3] libceph: add an option to configure client behavior when osds are full Josh Durgin
2013-12-03 23:12 ` [PATCH 3/3] rbd: document rbd-specific options Josh Durgin
2013-12-06 1:47 ` Josh Durgin [this message]
2013-12-06 4:58 ` [PATCH 0/3] block I/O when cluster is full Gregory Farnum
2013-12-07 2:16 ` Josh Durgin
2013-12-07 2:24 ` Gregory Farnum
2013-12-10 0:11 ` Josh Durgin
2013-12-10 0:19 ` Gregory Farnum
2013-12-10 0:45 ` Josh Durgin
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=52A12CA9.3020008@inktank.com \
--to=josh.durgin@inktank.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.