From: Martin Mailand <martin@tuxadero.com>
To: chb@muc.de
Cc: 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 13:49:25 +0200 [thread overview]
Message-ID: <4E9C1645.3070205@tuxadero.com> (raw)
In-Reply-To: <CAO47_-9qWX5cq-Qh9Kajt68ZCyzyhdsU5XTZ8MXSTj-s8+_XzA@mail.gmail.com>
Am 17.10.2011 11:40, schrieb Christian Brunner:
> 2011/10/15 Martin Mailand<martin@tuxadero.com>:
>> Hi Christian,
>> I have a very similar experience, I also used josef's tree and btrfs snaps =
>> 0, the next problem I had than was excessive fragmentation, so I used this
>> patch http://marc.info/?l=linux-btrfs&m=131495014823121&w=2, and changed the
>> btrfs option to (btrfs options = noatime,nodatacow,autodefrag) that kept the
>> fragmentation under control.
>> But even with this setup after a few days the load on the osd is unbearable.
>
> How did you find out about our fragmentation issues? Was it just a
> performance problem?
>
I used filefrag to show the number of extents, after the patch, I have
on average 1,14 extents per 4MB ceph object on the osd.
>> As far as I understood the doku if you disable the btrfs snapshot
>> functionality the writeahead journal is activated.
>> http://ceph.newdream.net/wiki/Ceph.conf
>> And I get this in the logs.
>> mount: enabling WRITEAHEAD journal mode: 'filestore btrfs snap' mode is not
>> enabled
>>
>> May I asked what kind of probs you did have with ext4? Because I am looking
>> into this direction as well.
>
> You can read about our ext4 problems here:
>
> http://marc.info/?l=ceph-devel&m=131201869703245&w=2
I still can reproduce the bug with v3.1-rc9.
>
> 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?
>
> Since I have just migrated to btrfs, I've some problems to check this,
> but I'll try to do this as soon as I can get hold of some extra
> hardware.
>
I can check this, I have a spare cluster at the moment.
> Regards,
> Christian
next prev parent reply other threads:[~2011-10-17 11:49 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 [this message]
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
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=4E9C1645.3070205@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--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.