[..]
>
>
> Yep, it`s same problem. It looks like bug. Manual udevadm trigger
> worked fine.
Good, seems like at least the ceph part is functioning correctly.
>
[..]
___
ceph-users mailing list
ceph-users@lists.ceph.com
Udev doesnt trigger at start. But i have correct rules at udev-rules file.
OS - debian jessie.ceph - jewel.
Hello,
I have a similar problem. I am not sure it's the same, but if i can help.
I'm in jewel ( upgrade from firefly ) on jessie.
The temporary solution that i
Hello,
I have a similar problem. I am not sure it's the same, but if i can help.
I'm in jewel ( upgrade from firefly ) on jessie.
The temporary solution that i found to start the OSD is to force udev to
launch its triggers :
udevadm trigger --action=add
Regards
--
On 12/08/2016 03:09 PM, Khramchikhin Nikolay wrote:
> No luck, i dont even have logs associate with ceph-disk at startup:
In that case your udev rules probably didn't trigger. Have a look in the
logs and see if udev invokes (/usr/sbin/ceph-disk --log-stdout -v
trigger /dev/$name)
you could
No luck, i dont even have logs associate with ceph-disk at startup:
$journalctl -u ceph-
it shows me only standart ceph services, such ceph-osd@
but after ceph-disk activate-lockbox, i can get logs:
journalctl -u
Hey Khramchikhin,
On 12/08/2016 12:22 PM, Khramchikhin Nikolay wrote:
> Hello, folks,
>
> I have problem with osd up after server reboot, all disk deployed with
> ceph-deploy osd prepare --dmcrypt, i `ve tried ceph-deploy osd create
> with no luck, same issue.
>
> After server reboot osd
Hello, folks,
I have problem with osd up after server reboot, all disk deployed with
ceph-deploy osd prepare --dmcrypt, i `ve tried ceph-deploy osd create
with no luck, same issue.
After server reboot osd dont come up, i need to run
*ceph-disk activate-lockbox /dev/sdb3 **
*
for
