All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ruben Kerkhof <ruben@rubenkerkhof.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: udev events on a disk, at boot time
Date: Tue, 21 Jun 2016 18:39:29 +0200	[thread overview]
Message-ID: <57696DC1.3090803@dachary.org> (raw)
In-Reply-To: <CAPed3OFeAJvLy+7G8YdwJ1pdi=p+tRatpPPQ=DmsvGjr-5QouA@mail.gmail.com>



On 21/06/2016 17:30, Ruben Kerkhof wrote:
> Dear Loic,
> 
> On Tue, Jun 21, 2016 at 4:35 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Ilya,
>>
>> On Debian Jessie 8.5 which has
>>
>> root@000000000000:/home/ubuntu# uname -a
>> Linux 000000000000.teuthology 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2 (2016-04-08) x86_64 GNU/Linux
>> root@000000000000:/home/ubuntu# udevadm --version
>> 215
>>
>> it looks like there are no udev ADD events at boot time and the OSD do not activate. After booting, if the disk is removed and re-added (via openstack server volume add / remove for instance), the OSD comes up as expected, which confirms the udev rules and the OSD are good.
>>
>> This can be worked around by running ceph-disk activate-all which scans all disks when run from /etc/init/ceph-osd-all-starter.conf at boot time. The workaround requires that /dev/disk/by-parttypeuuid is populated[1] and this can be done by installing the 60-ceph-partuuid-workaround.rules [2] file.
>>
>> Before trying to workaround the problem, I'd like to understand what is the difference with CentOS 7.2 which has
>>
>> # uname -a
>> Linux target167114254243.teuthology 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
>> # udevadm --version
>> 219
>>
>> and correctly fires the ADD events at boot time.
>>
>> A CentOS 7(minor version unknown) user reported the same problem as Debian Jessie 8.5 but I don't have information about the udev version nor the kernel version. I suspect this behavior has more to do with the udev + kernel version combination than with the distribution.
>>
>> I've not actually traced the udev events at boot time because I'm not sure how to do that. Hopefully you have an idea about why this is happening. Otherwise I'll try to collect hard evidence.
> 
> I think I'm seeing the exact same issue as you describe on CentOS 7.2,
> so this might not be limited to Debian Jessie.
> After a reboot the OSDs do not activate.
> With udev_log="debug" in /etc/udev/udev.conf, the journal doesn't show
> any sign that /usr/lib/udev/rules.d/95-ceph-osd.rules is executed.
> 
> ruben@hlm1-pod12-ceph03: ~$ udevadm --version
> 219
> 
> ruben@hlm1-pod12-ceph03: ~$ uname -a
> Linux hlm1-pod12-ceph03 3.10.0-327.18.2.el7.x86_64 #1 SMP Thu May 12
> 11:03:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> 
> Let me know if there's anything I can do to help debug this.

I wonder how my CentOS 7.2 setup is different. I'll try to reproduce the problem on CentOS 7.2 as well.

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre
--
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:[~2016-06-21 16:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 14:35 udev events on a disk, at boot time Loic Dachary
2016-06-21 15:30 ` Ruben Kerkhof
2016-06-21 16:39   ` Loic Dachary [this message]
2016-06-21 19:41     ` Alexandre DERUMIER
2016-06-22 11:33     ` Ruben Kerkhof
2016-06-22 12:20       ` Loic Dachary
2016-06-22 15:07         ` Ruben Kerkhof
2016-06-22 15:20           ` Loic Dachary

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=57696DC1.3090803@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ruben@rubenkerkhof.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.