All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Mailand <martin@tuxadero.com>
To: Sage Weil <sage@newdream.net>
Cc: chb@muc.de, Wido den Hollander <wido@widodh.nl>,
	ceph-devel@vger.kernel.org
Subject: Re: OSD blocked for more than 120 seconds
Date: Mon, 17 Oct 2011 20:06:35 +0200	[thread overview]
Message-ID: <4E9C6EAB.7070003@tuxadero.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1110170820040.22381@cobra.newdream.net>

Hi Sage,
the hang was on a btrfs, I do not have a fix for that.

The 'filestore flusher = false' does fix the ext4 problems, which where 
reported from Christian, but this option has quite an impact of the osd 
performance.
The '-o noauto_da_alloc' option did not solve the fsck problem.

Best Regards,
  Martin


Sage Weil schrieb:
> On Mon, 17 Oct 2011, Martin Mailand wrote:
>> Am 17.10.2011 11:40, schrieb Christian Brunner:
>>> Our bugreport with RedHat didn't make any progress for a long time,
>>> but last week RedHat made two sugestions:
>>>
>>> - If you configure ceph with 'filestore flusher = false', do you see
>>> any different behavior?
>>> - If you mount with -o noauto_da_alloc does it change anything?
>> Hi,
>> after a quick test I think 'filestore flusher = false' did the trick.
>> What does it do?
> 
> It fixes your hang (previous email), or the subsequent fsck errors?
> 
> When filestore flusher = true (default), after every write the fd is 
> handed off to another thread that uses sync_file_range() to push the data 
> out to disk quickly before closing the file.  The purpose is to limit the 
> latency for the eventual snapshot or sync.  Eric suspected the handoff 
> between threads may be what was triggering the bug in ext4.
> 
> sage

  reply	other threads:[~2011-10-17 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 20:39 OSD blocked for more than 120 seconds Martin Mailand
2011-10-14  9:38 ` Wido den Hollander
2011-10-15 19:33   ` Christian Brunner
2011-10-15 20:01     ` Martin Mailand
2011-10-17  9:40       ` Christian Brunner
2011-10-17 11:49         ` Martin Mailand
2011-10-17 12:05           ` Tomasz Paszkowski
2011-10-17 13:21             ` Martin Mailand
2011-10-17 14:13         ` Martin Mailand
2011-10-17 15:31           ` Sage Weil
2011-10-17 18:06             ` Martin Mailand [this message]
2011-10-17 18:24               ` Christian Brunner

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=4E9C6EAB.7070003@tuxadero.com \
    --to=martin@tuxadero.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=chb@muc.de \
    --cc=sage@newdream.net \
    --cc=wido@widodh.nl \
    /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.