On Sun, Sep 2, 2018 at 3:01 PM, David Wahler wrote:
> On Sun, Sep 2, 2018 at 1:31 PM Alfredo Deza wrote:
>>
>> On Sun, Sep 2, 2018 at 12:00 PM, David Wahler wrote:
>> > Ah, ceph-volume.log pointed out the actual problem:
>> >
>> > RuntimeError: Cannot use device (/dev/storage/bluestore). A vg/lv
On Sun, Sep 2, 2018 at 1:31 PM Alfredo Deza wrote:
>
> On Sun, Sep 2, 2018 at 12:00 PM, David Wahler wrote:
> > Ah, ceph-volume.log pointed out the actual problem:
> >
> > RuntimeError: Cannot use device (/dev/storage/bluestore). A vg/lv path
> > or an existing device is needed
>
> That is odd, i
On Sun, Sep 2, 2018 at 12:00 PM, David Wahler wrote:
> Ah, ceph-volume.log pointed out the actual problem:
>
> RuntimeError: Cannot use device (/dev/storage/bluestore). A vg/lv path
> or an existing device is needed
That is odd, is it possible that the error log wasn't the one that
matched what y
Ah, ceph-volume.log pointed out the actual problem:
RuntimeError: Cannot use device (/dev/storage/bluestore). A vg/lv path
or an existing device is needed
When I changed "--data /dev/storage/bluestore" to "--data
storage/bluestore", everything worked fine.
I agree that the ceph-deploy logs are a
There should be useful logs from ceph-volume in
/var/log/ceph/ceph-volume.log that might show a bit more here.
I would also try the command that fails directly on the server (sans
ceph-deploy) to see what is it that is actually failing. Seems like
the ceph-deploy log output is a bit out of order (
Hi all,
I'm attempting to get a small Mimic cluster running on ARM, starting
with a single node. Since there don't seem to be any Debian ARM64
packages in the official Ceph repository, I had to build from source,
which was fairly straightforward.
After installing the .deb packages that I built an
