From: Guido Winkelmann <guido-ceph@thisisnotatest.de>
To: ceph-devel@vger.kernel.org
Subject: Cannot mount ceph filesystem: error 5 (Input/Output error)
Date: Fri, 25 Nov 2011 17:53:15 +0100 [thread overview]
Message-ID: <4366451.BU1d1YAr76@pc10> (raw)
Hi,
When trying to mount a Ceph filesystem with "mount.ceph 10.3.1.33:6789:/ /mnt",
the command hangs for several minutes and then fails with the message
mount error 5 = Input/output error
Background:
I'm trying to set up a small 3-machine Ceph cluster, to be used for network-
transparent block- and file storage for Qemu server virtualization. This is the
first time I'm doing anything at all with Ceph, so many of the concepts are
still new and a bit confusing to me.
My plan was to set up each of the three machines equally with one mon, one osd
and one mds, and to add more servers, or replace the existing ones with bigger
machines, as need arises.
So far, I have only started with one of the three servers, to get at least a
basic configuration working and to get some feel for the system and its
components, before adding the other two.
The machines are all running a basic installation of CentOS 6. What I did so
far on the first machine was:
- Build a newer kernel (3.1.1) with built-in support for btrfs and ceph,
reboot with it
- Prepare two larger empty partitions (sda5 and sdb5) for data storage
- Download and unpack ceph-0.38.tar.gz, cd ceph-0.38
- Run ./configure
- Repeat numerous times while installing one dependency after the other,
eventually ending up with ./configure --without-fuse --without-tcmalloc
- make && make install
- Copy src/init-ceph to /etc/init.d/
- Create /usr/local/etc/ceph/ceph.conf with this content:
[global]
max open files = 131072
log file = /var/log/ceph/$name.log
log_to_syslog = true
pid file = /var/run/ceph/$name.pid
[mon]
mon data = /mondata/$name
[mon.ceph1]
host = ceph1
mon addr = 10.3.1.33:6789
[mds]
keyring = /cephxdata/keyring.$name
[mds.alpha]
host = ceph1
[osd]
osd data = /data/$name
osd journal = /data/$name/journal
osd journal size = 1000 ; journal size, in megabytes
[osd.0]
host = ceph1
btrfs devs = /dev/sda5 /dev/sdb5
(Slightly adjusted from src/sample.ceph.conf, comments removed for brevity)
- Run mkcephfs -c /usr/local/etc/ceph/ceph.conf --mkbtrfs -a -k \
/usr/local/etc/ceph/keyring.bin
- Run /etc/init.d/ceph start
After these steps, I tried to mount the ceph filesystem (on the same machine)
with "mount.ceph 10.3.1.33:6789:/ /mnt" and got the aforementioned error.
The only thing that happens in the logs when I try to mount is this one line
in mon log:
2011-11-25 17:26:53.216745 7f0ee75df700 -- 10.3.1.33:6789/0 >>
10.3.1.33:0/1719960241 pipe(0x7f0ee0001320 sd=12 pgs=0 cs=0 l=0).accept peer
addr is really 10.3.1.33:0/1719960241 (socket is 10.3.1.33:46908/0)
The osd and mds logs do not show any activity at that point.
Does anybody have any idea what could be going wrong here?
Guido
next reply other threads:[~2011-11-25 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 16:53 Guido Winkelmann [this message]
2011-11-25 18:54 ` Cannot mount ceph filesystem: error 5 (Input/Output error) Wido den Hollander
2011-12-02 16:24 ` Guido Winkelmann
2011-12-02 19:29 ` Samuel Just
2011-12-03 14:21 ` Guido Winkelmann
2011-12-06 19:51 ` Gregory Farnum
2011-12-07 14:38 ` Guido Winkelmann
2011-12-07 18:00 ` Tommi Virtanen
2011-12-07 18:03 ` Tommi Virtanen
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=4366451.BU1d1YAr76@pc10 \
--to=guido-ceph@thisisnotatest.de \
--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.