From: Wukongming <wu.kongming@h3c.com>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: ceph-osd activate timeout
Date: Thu, 13 Oct 2016 01:54:30 +0000 [thread overview]
Message-ID: <47D132BF400BE64BAE6D71033F7D3D7525256D5E@H3CMLB12-EX.srv.huawei-3com.com> (raw)
In-Reply-To: <47D132BF400BE64BAE6D71033F7D3D7525256C47@H3CMLB12-EX.srv.huawei-3com.com>
Hi All,
I noticed that sometime udev may receive a time-out message during activating osd after rebooting system. Sth like that:
Oct 11 07:15:40 cvknode2 udevd[965]: timeout: killing '/usr/sbin/ceph-disk activate-journal /dev/sdb2' [1834] Oct 11 07:15:40 cvknode2 udevd[965]: '/usr/sbin/ceph-disk activate-journal /dev/sdb2' [1834] terminated by signal 9 (Killed)
It will cause device or partition mounted on both directory, the right one and tmp one.
/dev/sdb1 477630464 218421512 259208952 46% /var/lib/ceph/tmp/mnt.rzE_fa
/dev/sdb1 477630464 218421512 259208952 46% /var/lib/ceph/osd/ceph-2
When I commented out all in the /lib/udev/rules.d/95-ceph-osd.rules and rebooted system, there would be no timeout and osd could be activated normally. I have 2 questions:
1. What caused udev receive timeout message.
2. Can I just commented out all in the /lib/udev/rules.d/95-ceph-osd.rules, Cause calling activate-all can do activate osds, why need extra calling activate and activate-journal?
Best regards,
---------------------------------------------
wukongming ID: 12019
Tel：0571-86760239
Dept：ONEStor RD
-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!
parent reply other threads:[~2016-10-13 2:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <47D132BF400BE64BAE6D71033F7D3D7525256C47@H3CMLB12-EX.srv.huawei-3com.com>]
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=47D132BF400BE64BAE6D71033F7D3D7525256D5E@H3CMLB12-EX.srv.huawei-3com.com \
--to=wu.kongming@h3c.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.com \
/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.