CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: puzzling disapearance of /dev/sdc1
Date: Thu, 17 Dec 2015 13:30:15 +0100	[thread overview]
Message-ID: <5672AAD7.8030004@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 958 bytes --]

Hi Ilya,

This is another puzzling behavior (the log of all commands is at http://tracker.ceph.com/issues/14094#note-4). in a nutshell, after a series of sgdisk -i commands to examine various devices including /dev/sdc1, the /dev/sdc1 file disappears (and I think it will showup again although I don't have a definitive proof of this).

It looks like a side effect of a previous partprobe command, the only command I can think of that removes / re-adds devices. I thought calling udevadm settle after running partprobe would be enough to ensure partprobe completed (and since it takes as much as 2mn30 to return, I would be shocked if it does not ;-).

Any idea ? I desperately try to find a consistent behavior, something reliable that we could use to say : "wait for the partition table to be up to date in the kernel and all udev events generated by the partition table update to complete". 

Cheers
-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-12-17 12:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 12:30 Loic Dachary [this message]
2015-12-17 13:31 ` puzzling disapearance of /dev/sdc1 Sage Weil
2015-12-17 14:10   ` Loic Dachary
2015-12-17 16:26     ` Ilya Dryomov
2015-12-18 12:38       ` Loic Dachary
2015-12-18 15:31         ` Ilya Dryomov
2015-12-18 16:23           ` Loic Dachary
2015-12-18 16:32             ` Loic Dachary
2015-12-18 16:34               ` 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=5672AAD7.8030004@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox