From: Martin Mailand <martin@tuxadero.com>
To: Tomasz Paszkowski <ss7pro@gmail.com>
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 15:21:46 +0200 [thread overview]
Message-ID: <4E9C2BEA.70002@tuxadero.com> (raw)
In-Reply-To: <CAMvP8PC9j1V20HR1a1mTWVJKT+cbsbAHiigz+2XwBGm14dU7mw@mail.gmail.com>
Am 17.10.2011 14:05, schrieb Tomasz Paszkowski:
> Hi,
>
> It seems that ext4 and btrfs are not to be considered as stable for
> now. Does anyone could confirm that
> ext3 is the best choice for this moment ?
Hi,
I did a quick test with ext3, and it did not look very good.
After a few minutes one of the osds failed with this message.
[315274.737204] kjournald starting. Commit interval 5 seconds
[315274.737919] EXT3-fs (sdb): using internal journal
[315274.737929] EXT3-fs (sdb): mounted filesystem with ordered data mode
[317040.890148] INFO: task ceph-osd:18032 blocked for more than 120 seconds.
[317040.905855] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[317040.923801] ceph-osd D ffff880114c8b1a0 0 18032 1
0x00000000
[317040.923812] ffff88010f2e3cb8 0000000000000086 ffff88010f2e3cb8
ffff88010f2e3cb8
[317040.923821] ffff88011ffdff08 ffff88010f2e3fd8 ffff88010f2e2000
ffff88010f2e3fd8
[317040.923830] ffff880116dadbc0 ffff880114c8ade0 ffff88010f2e3cd8
ffffffff8110d500
[317040.923847] Call Trace:
[317040.923865] [<ffffffff8110d500>] ? find_get_pages_tag+0x40/0x130
[317040.923876] [<ffffffff815d93df>] schedule+0x3f/0x60
[317040.923884] [<ffffffff815d99ed>] schedule_timeout+0x26d/0x2e0
[317040.923893] [<ffffffff8101a725>] ? native_sched_clock+0x15/0x70
[317040.923899] [<ffffffff8101a789>] ? sched_clock+0x9/0x10
[317040.923908] [<ffffffff8108d465>] ? sched_clock_local+0x25/0x90
[317040.923916] [<ffffffff815d9219>] wait_for_common+0xd9/0x180
[317040.923924] [<ffffffff8105bbc0>] ? try_to_wake_up+0x2b0/0x2b0
[317040.923932] [<ffffffff815d939d>] wait_for_completion+0x1d/0x20
[317040.923941] [<ffffffff8118d652>] sync_inodes_sb+0x92/0x1c0
[317040.923949] [<ffffffff81192440>] ? __sync_filesystem+0x90/0x90
[317040.923956] [<ffffffff81192430>] __sync_filesystem+0x80/0x90
[317040.923963] [<ffffffff8119245f>] sync_one_sb+0x1f/0x30
[317040.923972] [<ffffffff81169268>] iterate_supers+0xa8/0x100
[317040.923979] [<ffffffff81192360>] sync_filesystems+0x20/0x30
[317040.923985] [<ffffffff81192501>] sys_sync+0x21/0x40
[317040.923995] [<ffffffff815e37c2>] system_call_fastpath+0x16/0x1b
Best Regards,
martin
next prev parent reply other threads:[~2011-10-17 13:21 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 [this message]
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=4E9C2BEA.70002@tuxadero.com \
--to=martin@tuxadero.com \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@muc.de \
--cc=ss7pro@gmail.com \
--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.