All of lore.kernel.org
 help / color / mirror / Atom feed
From: femi anjorin <femi.anjorin@gmail.com>
To: ceph-devel@vger.kernel.org
Subject: Re: CEPHFS mount error !!!
Date: Thu, 7 Feb 2013 12:05:24 +0100	[thread overview]
Message-ID: <CAPhYxPwRWk8H5nE9yhWECtRShM0ABZ3WBTcEBfL2sS7ZRNgjUA@mail.gmail.com> (raw)
In-Reply-To: <511276DB.3010101@bmrb.wisc.edu>

Hi ... I am now testing cephfs on an ubuntu client before going back to centos.

A quick question about this command:
mount -t ceph 192.168.0.1:6789:/ /mnt/mycephfs -o
name=admin,secretfile=/etc/ceph/admin.secret ?
mount -t ceph 192.168.0.1:6789:/ /mnt/mycephfs -o
name=ceph,secretfile=/etc/ceph/ceph.keyring ?

Does it need admin.secret  or can i use ceph.keyring to mount with
cephfs file system?

Just a note: At the initial setup of the cluster i used:
mkcephfs -c /etc/ceph/ceph.conf --mkfs -a -k  /etc/ceph/ceph.keyring.

So i only have ceph.keyring NOT admin.secret ....


if i do:

#mount -t ceph 172.16.0.25:6789:/ /mnt/mycephfs
mount error 22 = Invalid argument
#dmesg
[ 7182.027665] libceph: client0 fsid 31c4d83e-cb0a-4fed-ab6f-581e8d5356f5
[ 7182.027715] libceph: no secret set (for auth_x protocol)
[ 7182.027719] libceph: error -22 on auth protocol 2 init


#mount -t ceph 172.16.0.25:6789:/ /mnt/mycephfs -o
name=ceph,secretfile=/etc/ceph/ceph.keyring
secret is not valid base64: Invalid argument.
adding ceph secret key to kernel failed: Invalid argument.
failed to parse ceph_options
#dmesg
[ 7639.377337] libceph: client0 fsid 31c4d83e-cb0a-4fed-ab6f-581e8d5356f5
[ 7639.378047] libceph: auth method 'x' error -1


Regards,
Femi







On Wed, Feb 6, 2013 at 4:29 PM, Dimitri Maziuk <dmaziuk@bmrb.wisc.edu> wrote:
> On 2/6/2013 5:54 AM, Dennis Jacobfeuerborn wrote:
> ...
>
>>> To mount cephfs like that you need to have kernel support. As the Linux
>>> kernel on CentOS 6.3 is version 2.6.32 and Ceph support wasn't added
>>> until
>>> 2.6.34, you need to compile your own kernel.
>>>
>>
>> The better alternative is probably to install a kernel from
>> http://elrepo.org/tiki/kernel-lt . "lt" stand for "long term" and should
>> be
>> fairly stable and "ml" is "mainline" which is even more current but
>> because
>> of that not quite as stable (currently 3.7.6).
>
>
> I had problems booting ml on some/most (dep. on the version) our machines,
> plus it's a pain to track: there's a new one every day.
>
> I do have lt running without problems and mounting cephfs, however, I
> haven't gotten around to the actual ceph testing on it yet so I can't say
> anything about ceph client's performance/stability on it. ("lt" is 3.0, as
> I
> understand it doesn't have the latest and greatest ceph module(?))
>
> Dimitri
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-02-07 11:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  5:37 CEPHFS mount error !!! femi anjorin
2013-02-06  6:55 ` Dan Mick
2013-02-06  7:20   ` femi anjorin
2013-02-06  7:24     ` Jens Kristian Søgaard
2013-02-06 11:54       ` Dennis Jacobfeuerborn
2013-02-06 15:29         ` Dimitri Maziuk
2013-02-07 11:05           ` femi anjorin [this message]
2013-02-07 20:12             ` Dan Mick

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=CAPhYxPwRWk8H5nE9yhWECtRShM0ABZ3WBTcEBfL2sS7ZRNgjUA@mail.gmail.com \
    --to=femi.anjorin@gmail.com \
    --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.