From: Wido den Hollander <wido@widodh.nl>
To: Marcin Szukala <szukala.marcin@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: Ceph version 0.56.1, data loss on power failure
Date: Wed, 16 Jan 2013 11:53:22 +0100 [thread overview]
Message-ID: <50F686A2.2060901@widodh.nl> (raw)
In-Reply-To: <CA+-7kDCLhNx3QQ3OUGxrKT6VJszyPuPdgceA8C-pqYZRBqKkZQ@mail.gmail.com>
On 01/16/2013 11:50 AM, Marcin Szukala wrote:
> Hi all,
>
> Any ideas how can I resolve my issue? Or where the problem is?
>
> Let me describe the issue.
> Host boots up and maps RBD image with XFS filesystems
> Host mounts the filesystems from the RBD image
> Host starts to write data to the mounted filesystems
> Host experiences power failure
> Host comes up and map the RBD image
> Host mounts the filesystems from the RBD image
> All data from all filesystems is lost
> Host is able to use the filesystems with no problems.
>
> Filesystem is XFS, no errors on filesystem,
>
That simply does not make sense to me. How can all data be gone and the
FS just mount cleanly.
Can you try to format the RBD with EXT4 and see if that makes any
difference.
Could you also try to run a "sync" prior to pulling the power from the
host to see if that makes any difference.
Wido
> Kernel 3.5.0-19-generic
>
> root@openstack-1:/etc/init# ceph -s
> health HEALTH_OK
> monmap e1: 3 mons at
> {a=10.3.82.102:6789/0,b=10.3.82.103:6789/0,d=10.3.82.105:6789/0},
> election epoch 10, quorum 0,1,2 a,b,d
> osdmap e132: 56 osds: 56 up, 56 in
> pgmap v87165: 13744 pgs: 13744 active+clean; 52727 MB data, 102 GB
> used, 52028 GB / 52131 GB avail
> mdsmap e1: 0/0/1 up
>
> Regards,
> Marcin
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-01-16 10:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 13:54 Ceph version 0.56.1, data loss on power failure Marcin Szukala
2013-01-10 13:58 ` Wido den Hollander
2013-01-10 14:40 ` Sylvain Munaut
2013-01-10 16:56 ` Marcin Szukala
2013-01-10 22:12 ` Gregory Farnum
2013-01-11 11:07 ` Marcin Szukala
2013-01-11 19:34 ` Gregory Farnum
2013-01-11 22:02 ` Marcin Szukala
2013-01-16 10:50 ` Marcin Szukala
2013-01-16 10:53 ` Wido den Hollander [this message]
2013-01-16 14:09 ` Yann Dupont
2013-01-16 14:32 ` Marcin Szukala
2013-01-16 16:56 ` Jeff Mitchell
2013-01-17 8:37 ` Yann Dupont
2013-01-16 14:10 ` Dino Yancey
2013-01-16 14:28 ` Marcin Szukala
2013-01-16 17:00 ` Sage Weil
2013-01-16 17:06 ` Wido den Hollander
2013-01-16 18:10 ` Sage Weil
2013-01-16 20:48 ` Tomasz Paszkowski
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=50F686A2.2060901@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=szukala.marcin@gmail.com \
/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.