From: Wido den Hollander <wido@widodh.nl>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: btrfs_alloc_free_block
Date: Thu, 12 Apr 2012 10:45:23 +0200 [thread overview]
Message-ID: <4F869623.7000005@widodh.nl> (raw)
Hi,
I just noticed some issues in my cluster where a couple of OSDs would
commit suicide due to I/O timeouts.
A quick check showed me: http://pastebin.com/uU1MJRPh
I killed (clean shutdown) osd.1 in this case and tried to start it
again, that seemed to go well, but then the btrfs mount failed:
http://pastebin.com/F1nSb67y
"btrfs: open_ctree failed"
root@atom0:/var/log/ceph# service ceph start osd.1
=== osd.1 ===
Mounting Btrfs on atom0:/var/lib/ceph/osd.1
Scanning for Btrfs filesystems
mount: wrong fs type, bad option, bad superblock on /dev/sdc,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
failed: 'modprobe btrfs ; btrfs device scan || btrfsctl -a ; egrep -q
'^[^ ]+ /var/lib/ceph/osd.1' /proc/mounts || mount -t btrfs -o noatime
/dev/disk/by-id/scsi-SATA_WDC_WD20EARS-00_WD-WCAZA3231872
/var/lib/ceph/osd.1'
root@atom0:/var/log/ceph#
Has anyone seen this behavior with the 3.3.0 kernel?
My main concern is the fact that my filesystem won't mount anymore and I
have to re-format the whole OSD. This open_ctree problem keeps coming back.
Wido
reply other threads:[~2012-04-12 8:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F869623.7000005@widodh.nl \
--to=wido@widodh.nl \
--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.