On Thu, 17 Dec 2015, Loic Dachary wrote: > 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".
I wonder if the underlying issue is that we shouldn't be calling udevadm settle from something running from udev. Instead, of a udev-triggered run of ceph-disk does something that changes the partitions, it should just exit and let udevadm run ceph-disk again on the new devices...? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html