From: Adam Nielsen <a.nielsen@shikadi.net>
To: ceph-devel@vger.kernel.org
Subject: Unable to mount cephfs - can't read superblock
Date: Sat, 09 Feb 2013 20:40:02 +1000 [thread overview]
Message-ID: <kf5920$1de$1@ger.gmane.org> (raw)
Hi again,
I'm trying to mount my new Ceph volume on a remote PC using cephfs. I've
followed the quick start guide, but when I try to mount the filesystem I get this:
remote$ mount -t ceph 192.168.0.6:6789:/ /mnt/ceph/
mount: 192.168.0.6:6789:/: can't read superblock
remote$ dmesg | tail
[951382.981690] libceph: client4105 fsid aa447ff8-8270-491b-b59e-2735e852eaf5
[951382.983486] libceph: mon0 192.168.0.6:6789 session established
I'm not sure what the problem is. The osd, mon and mds daemons are running on
the Ceph host and no traffic is firewalled between the two machines. I have
disabled authentication in ceph.conf. The only issue I can see is this:
cephhost$ ceph health
HEALTH_WARN 192 pgs degraded; 192 pgs stuck unclean
I'm not sure what that means as I have only used mkcephfs and then started the
ceph service. I haven't actually used it yet so I'm not sure where the
unclean pgs are coming from. The underlying filesystem is ext4 though.
I'm a bit stuck as to what to do next. I can't see why the filesystem won't
mount remotely, and the troubleshooting docs say unclean pgs are related to
outages which doesn't seem possible on a newly created volume with only one
osd/mon/mds instance.
Any pointers would be much appreciated!
Many thanks,
Adam.
next reply other threads:[~2013-02-09 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 10:40 Adam Nielsen [this message]
2013-02-09 10:42 ` Unable to mount cephfs - can't read superblock Wido den Hollander
2013-02-09 11:06 ` Adam Nielsen
2013-02-09 11:09 ` Wido den Hollander
2013-02-09 11:25 ` Adam Nielsen
2013-02-11 22:47 ` Ross David Turk
2013-03-05 1:06 ` GMane for ceph-users (was Re: Unable to mount cephfs - can't read superblock) Ross David Turk
2013-02-09 16:37 ` Unable to mount cephfs - can't read superblock Gregory Farnum
2013-02-09 22:13 ` Adam Nielsen
2013-02-11 20:16 ` Gregory Farnum
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='kf5920$1de$1@ger.gmane.org' \
--to=a.nielsen@shikadi.net \
--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.