From: Dan Mick <dan.mick@inktank.com>
To: Eric_YH_Chen@wiwynn.com
Cc: ceph-devel@vger.kernel.org
Subject: Re: accident corruption in osdmap
Date: Wed, 08 Aug 2012 20:53:53 -0700 [thread overview]
Message-ID: <50233451.1060204@inktank.com> (raw)
In-Reply-To: <60E83269D669544E8069A09CB69135EA01C298@GDC-CLDMBX-P02.whq.wistron>
On 08/08/2012 08:19 PM, Eric_YH_Chen@wiwynn.com wrote:
> Dear all:
>
> My Environment: two servers, and 12 hard-disk on each server.
> Version: Ceph 0.48, Kernel: 3.2.0-27
>
> We create a ceph cluster with 24 osd, 3 monitors
> Osd.0 ~ osd.11 is on server1
> Osd.12 ~ osd.23 is on server2
> Mon.0 is on server1
> Mon.1 is on server2
> Mon.2 is on server3 which has no osd
>
> We create a rbd device and mount it as ext4 file system.
> During read/write data on the rbd device, one of the storage server is shutdown by accident.
> After reboot the server, we cannot access the rbd device any more.
> One of the log shows the osdmap is corrupted.
>
> Aug 5 15:37:24 ubuntu-002 kernel: [78579.998582] libceph: corrupt inc osdmap epoch 78 off 98 (ffffc9000177d07e of ffffc9000177d01c-ffffc9000177edf2)
>
> We would like to know what kind of scenario would cause the corruption of osdmap and how to avoid it?
> It seems that osdmap corruption cannot be recovered by the ceph cluster itself.
>
> Is it the same issue with http://tracker.newdream.net/issues/2446?
> In which version of kernel that we can find this patch? Thanks!
I'm not sure if it's the same issue, but looking at the Linux kernel
tree, it seems as though that fix is in v3.5-rc1
next prev parent reply other threads:[~2012-08-09 3:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 3:19 accident corruption in osdmap Eric_YH_Chen
2012-08-09 3:53 ` Dan Mick [this message]
2012-08-09 15:53 ` Sage Weil
2012-08-09 19:29 ` Stefan Kleijkers
2012-08-10 2:24 ` Eric_YH_Chen
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=50233451.1060204@inktank.com \
--to=dan.mick@inktank.com \
--cc=Eric_YH_Chen@wiwynn.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.