Hi Sage, I set up a simple virtual cluster to test this today, and it appears that all is well. The issue I was attempting to fix doesn't appear to be present in wip-firefly-dmcrypt's ceph-disk.
Steve On Tue, Aug 12, 2014 at 10:39 AM, Sage Weil <[email protected]> wrote: > Hi Steve, > > We ran into a problem with the ceph-disk changes back in 67339470 (they > were breaking dmcrypt when the journal was on a separate device). At the > same time we resolved another bug. With your change reverted, and the new > fix, and other changes to ceph-disk since then, it appears to be working > fine for all of my tests. > > Do you mind testing the ceph-disk from wip-firefly-dmcrypt in your > environment to verify that you don't see the original problem? The > explanation in your original commit sounds plausible (that the kernel > wouldn't refresh the partition table if dmcrypt was consuming one of the > partitions), but it just doesn't seem to be the case for me. > > Thanks! > sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
