From: Thomas Mueller <thomas@chaschperli.ch>
To: ceph-devel@vger.kernel.org
Subject: crush update failure ("corrupt inc osdmap epoch 5 off 50")
Date: Wed, 16 Jun 2010 06:32:46 +0000 (UTC) [thread overview]
Message-ID: <hv9r6e$4tp$1@dough.gmane.org> (raw)
hi
i tried to change data "max_size" to 1 to disable replication for testing.
what i've done (reproducable):
mkcephfs -c /etc/ceph/ceph.conf --mkbtrfs (1mds, 1mon, 2osd (2 phyiscal disks))
start ceph
mount ceph fs
write some files to the mount
ceph osd getcrushmap -o /tmp/crush
crushtool -d /tmp/crush -o /tmp/crush.txt
change data "max_size 10" to "max_size 1" in /tmp/crush.txt
crushtool -c /tmp/crush.txt -o /tmp/crush.new
ceph osd setcrushmap -i /tmp/crush.new (Output:
* read 428 bytes from /tmp/crush.new
* 10.06.16_08:12:57.187556 41223950 monclient(hunting): found mon0
* 10.06.16_08:12:57.188298 mon <- [osd,setcrushmap]
* 10.06.16_08:12:58.303241 mon0 -> 'set crush map' (0)
)
after starting to write a file to the mount, I see these kernel messages :
http://pastebin.com/maVj9daV
ceph / kclient are yesterdays git unstable / unstable-backport versions.
kernel is debian lenny backport 2.6.32.
- Thomas
next reply other threads:[~2010-06-16 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 6:32 Thomas Mueller [this message]
2010-06-16 16:57 ` crush update failure ("corrupt inc osdmap epoch 5 off 50") Sage Weil
2010-06-17 8:41 ` Thomas Mueller
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='hv9r6e$4tp$1@dough.gmane.org' \
--to=thomas@chaschperli.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox