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: Wed, 22 Jun 2016 17:20:52 +0200	[thread overview]
Message-ID: <576AACD4.80406@dachary.org> (raw)
In-Reply-To: <CAPed3OGUMDjsDTZsb-eNBmoZ9Qjffdb8uXeYG=07Y4D9kbb8mA@mail.gmail.com>

Yeah ! One more clue :-)

On 22/06/2016 17:07, Ruben Kerkhof wrote:
> On Wed, Jun 22, 2016 at 2:20 PM, Loic Dachary <loic@dachary.org> wrote:
>>> One thing that might be different between our setups is that my root
>>> fs is on LVM. I'll reinstall a server just to see if that matters.
>>>
>>> Another workaround for this that works for me is running 'udevadm
>>> trigger -c add -s block' after boot, this mounts the ceph volumes
>>> successfully.
>>
>> Thanks for the additional information. It confirms that for some reason I have ADD events in my test setup and you don't. Still digging.
> 
> I now reinstalled a few servers with the root fs on a plain partition,
> to take LVM out of the equation, and the OSDs come up fine.
> 

-- 
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-22 15:21 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
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 [this message]

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=576AACD4.80406@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.