From: Karol Jurak <karol.jurak@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Journal too small
Date: Thu, 17 May 2012 12:59:55 +0200 [thread overview]
Message-ID: <201205171259.55967.karol.jurak@gmail.com> (raw)
Hi,
During an ongoing recovery in one of my clusters a couple of OSDs
complained about too small journal. For instance:
2012-05-12 13:31:04.034144 7f491061d700 1 journal check_for_full at
863363072 : JOURNAL FULL 863363072 >= 1048571903 (max_size 1048576000
start 863363072)
2012-05-12 13:31:04.034680 7f491061d700 0 journal JOURNAL TOO SMALL: item
1693745152 > journal 1048571904 (usable)
I was under the impression that the OSDs stopped participating in recovery
after this event. (ceph -w showed that the number of PGs in state
active+clean no longer increased.) They resumed recovery after I enlarged
their journals (stop osd, --flush-journal, --mkjournal, start osd).
How serious is such situation? Do the OSDs know how to handle it
correctly? Or could this result in some data loss or corruption? After the
recovery finished (ceph -w showed that all PGs are in active+clean state)
I noticed that a few rbd images were corrupted.
The cluster runs v0.46. The OSDs use ext4. I'm pretty sure that during the
recovery no clients were accessing the cluster.
Best regards,
Karol
next reply other threads:[~2012-05-17 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 10:59 Karol Jurak [this message]
2012-05-17 16:01 ` Journal too small Sage Weil
2012-05-17 17:00 ` Tommi Virtanen
2012-05-17 17:33 ` Sage Weil
2012-05-18 10:58 ` Karol Jurak
2012-05-17 18:59 ` Josh Durgin
2012-05-18 10:56 ` Karol Jurak
2012-05-19 1:51 ` Josh Durgin
2012-05-21 15:11 ` Karol Jurak
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=201205171259.55967.karol.jurak@gmail.com \
--to=karol.jurak@gmail.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.