From: Zenon Panoussis <oracle@provocation.net>
To: ceph-devel@vger.kernel.org
Subject: Re: mount.ceph: modprobe failed, exit status 127
Date: Fri, 15 Apr 2011 14:57:02 +0200 [thread overview]
Message-ID: <4DA8409E.9000808@provocation.net> (raw)
In-Reply-To: <4DA82A9E.5010504@science-computing.de>
On 04/15/2011 01:23 PM, Christoph Raible wrote:
> I compiled new kernel on CentOS 5.6 (kernel-ml-2.6.38-2) with CEPH support
> CONFIG_CEPH_LIB=y
> # CONFIG_CEPH_LIB_PRETTYDEBUG is not set
> CONFIG_CEPH_FS=y
This builds the drivers into the kernel. For loadable modules you should use
CONFIG_CEPH_LIB=m and CONFIG_CEPH_FS=m .
> Now when I want to mount a Ceph filesystem with
> mount -t ceph 10.1.9.46:/ /mnt/ceph
> I got following error:
> "mount.ceph: modprobe failed, exit status 127"
Since ceph and libceph are already in the kernel, it seems logical that loading
them would fail; after all, there are no modules to be loaded. Then again, it
doesn't make sense that mount tries to load them anyway and fails.
Z
next prev parent reply other threads:[~2011-04-15 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 11:23 mount.ceph: modprobe failed, exit status 127 Christoph Raible
2011-04-15 12:57 ` Zenon Panoussis [this message]
2011-04-15 16:43 ` Tommi Virtanen
2011-04-18 11:50 ` Christoph Raible
2011-04-18 16:28 ` 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=4DA8409E.9000808@provocation.net \
--to=oracle@provocation.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.