From: Prashanth Nednoor <Prashanth.nednoor@taec.toshiba.com>
To: ceph-devel@vger.kernel.org
Subject: Having issues trying to get the OSD up on a MIPS64!!!
Date: Thu, 23 Oct 2014 01:28:28 +0000 (UTC) [thread overview]
Message-ID: <loom.20141023T030922-990@post.gmane.org> (raw)
Hello Everyone,
We are using ceph-0.86, good news is we were able to compile and load
all the libraries and binaries needed to configure a CEPH-OSD on MIPS 64
platform. The CEPH monitor is also able to detect the OSD, but not up
yet, as the osd activate failed.
Since we don’t have the required CEPH deploy utility for MIPS64, we are
following the manual procedure to create and activate an OSD.
We have disabled authentication between the clients and the OSD’s for
now.
Has any body tried CEPH on a MIPS64?
/dev/sda is a 2TB local hard drive.
This is how my partition looks after ceph-disk-prepare
/home/prashan/ceph-0.86/src# parted
GNU Parted 2.3
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: ATA TOSHIBA MQ01ABB2 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start End Size File system Name Flags
2 1049kB 5369MB 5368MB ceph journal
1 5370MB 2000GB 1995GB xfs ceph data
The following are the steps to create an OSD
1) ceph-disk zap /dev/sda
2) ceph-disk-prepare --cluster f615496c-b40a-4905-bbcd-
2d3e181ff21a --fs-type xfs /dev/sda
3) mount /dev/sda1 /var/lib/ceph/osd/ceph-0/
4) ceph-osd -i 0 –mkfs is giving an error ,
filestore(/var/lib/ceph/osd/ceph-0) could not find
23c2fcde/osd_superblock/0//-1 in index: (2) No such file.
After this it segfaults. We have analyzed this further with the help of
strace and root caused this as objectmap file reading issue.
open("/var/lib/ceph/osd/ceph-0/current/omap/000005.log", O_RDONLY) = 11,
the first time it reads 32k, the read succeeds with 63 bytes and it
tries to read again with 27k and the read returns 0 bytes and the CEPH
osd segfaults.
Please note that ceph-disk prepare creates a journal in a path which is
not valid(dev/disk/by-partuuid/cbd4a5d1-012f-4863-b492-080ad2a505cb).
So after step3 above I remove this journal below and manually create a
journal file before doing step4 above.
ls -l /var/lib/ceph/osd/ceph-0/
total 16
-rw-r--r-- 1 root root 37 Oct 22 21:40 ceph_fsid
-rw-r--r-- 1 root root 37 Oct 22 21:40 fsid
lrwxrwxrwx 1 root root 58 Oct 22 21:40 journal -> /dev/disk/by-
partuuid/cbd4a5d1-012f-4863-b492-080ad2a505cb
-rw-r--r-- 1 root root 37 Oct 22 21:40 journal_uuid
-rw-r--r-- 1 root root 21 Oct 22 21:40 magic
Any pointers to move ahead will be greatly appreciated??
thanks
Prashanth
--
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
next reply other threads:[~2014-10-23 1:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 1:28 Prashanth Nednoor [this message]
2014-10-24 0:53 ` Having issues trying to get the OSD up on a MIPS64!!! Sage Weil
2014-10-24 21:38 ` Prashanth Nednoor
2014-10-25 0:47 ` Sage Weil
2014-10-25 0:55 ` Philip Kufeldt
2014-10-25 1:11 ` Sage Weil
2014-10-27 2:31 ` Prashanth Nednoor
2014-10-27 4:14 ` Prashanth Nednoor
2015-02-17 7:58 ` Bao Vu
2015-02-17 14:06 ` Sage Weil
2015-02-17 16:57 ` Bao Vu
2015-02-17 17:06 ` Sage Weil
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=loom.20141023T030922-990@post.gmane.org \
--to=prashanth.nednoor@taec.toshiba.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.