OK, so nuked everything Ceph-related on my nodes, and started over. Now running
Jewel (ceph version 10.2.2). Everything went fine until "ceph-deploy osd
activate” again; now I’m seeing the following --
[ceph_deploy.osd][DEBUG ] activating host ceph2 disk /dev/sdc
[ceph_deploy.osd][DEBUG ] will use init type: systemd
[ceph2][DEBUG ] find the location of an executable
[ceph2][INFO ] Running command: sudo /usr/sbin/ceph-disk -v activate
--mark-init systemd --mount /dev/sdc
[ceph2][WARNIN] main_activate: path = /dev/sdc
[ceph2][WARNIN] get_dm_uuid: get_dm_uuid /dev/sdc uuid path is
/sys/dev/block/8:32/dm/uuid
[ceph2][WARNIN] command: Running command: /sbin/blkid -p -s TYPE -o value --
/dev/sdc
[ceph2][WARNIN] Traceback (most recent call last):
[ceph2][WARNIN] File "/usr/sbin/ceph-disk", line 9, in <module>
[ceph2][WARNIN] load_entry_point('ceph-disk==1.0.0', 'console_scripts',
'ceph-disk')()
[ceph2][WARNIN] File "/usr/lib/python2.7/site-packages/ceph_disk/main.py",
line 4994, in run
[ceph2][WARNIN] main(sys.argv[1:])
[ceph2][WARNIN] File "/usr/lib/python2.7/site-packages/ceph_disk/main.py",
line 4945, in main
[ceph2][WARNIN] args.func(args)
[ceph2][WARNIN] File "/usr/lib/python2.7/site-packages/ceph_disk/main.py",
line 3299, in main_activate
[ceph2][WARNIN] reactivate=args.reactivate,
[ceph2][WARNIN] File "/usr/lib/python2.7/site-packages/ceph_disk/main.py",
line 3009, in mount_activate
[ceph2][WARNIN] e,
[ceph2][WARNIN] ceph_disk.main.FilesystemTypeError: Cannot discover filesystem
type: device /dev/sdc: Line is truncated:
[ceph2][ERROR ] RuntimeError: command returned non-zero exit status: 1
[ceph_deploy][ERROR ] RuntimeError: Failed to execute command:
/usr/sbin/ceph-disk -v activate --mark-init systemd --mount /dev/sdc
Still the same sort of error… no output from the blkid command used. Again, if
I use either “-s PTTYPE” or get rid of the “-s TYPE” altogether, I get a value
returned (“gpt”)…
> On Jul 16, 2016, at 11:10 AM, Will Dennis <[email protected]> wrote:
>
> So in doing more reading, I see that I’m using a really old version (Firefly)
> that I got out of the EPEL repo… Was initially following instructions from
> the Packt book "Learning Ceph” which I now see came out in Jan 2015… Think
> I’ll nuke my current Ceph deployment and start over following the
> instructions in http://docs.ceph.com/docs/master/start/quick-ceph-deploy/
> <http://docs.ceph.com/docs/master/start/quick-ceph-deploy/> from the
> beginning, and see if that works better.
>
>
>> On Jul 16, 2016, at 10:44 AM, Will Dennis <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> ceph2 | SUCCESS | rc=0 >>
>> ceph version 0.80.7 (6c0127fcb58008793d3c8b62d925bc91963672a3)
>>
>> ceph3 | SUCCESS | rc=0 >>
>> ceph version 0.80.7 (6c0127fcb58008793d3c8b62d925bc91963672a3)
>>
>> ceph4 | SUCCESS | rc=0 >>
>> ceph version 0.80.7 (6c0127fcb58008793d3c8b62d925bc91963672a3)
>>
>> Yes, I thought that using sysvinit was strange too, but I didn’t know what
>> to expect… Wonder where that went off the rails?
>>
>>
>>> On Jul 16, 2016, at 3:45 AM, Wido den Hollander <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>> Which version of Ceph are you testing with?
>>>
>>> I see 'will use init type: sysvinit' which is odd, since Ceph version Jewel
>>> uses systemd.
>>>
>>> Wido
>
_______________________________________________
ceph-users mailing list
[email protected]
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
