Hi Bruce,
I think the problem comes from using /dev/disk/by-id/wwn-0x53959bd02f56
instead of /dev/sdw for the data disk, because ceph-disk has a device name
parsing logic that works with /dev/XXX. Could you run the ceph-disk prepare
command again with --verbose to confirm ? If that's the ca
Hi Reid,
Yes they will, but if the object which the user is writing to (Disk Block if
using RBD, which then maps to an object) has never been written to before,
it won't have to promote the object from the base pool before being able to
write it.
However as you write each object, once the cache p
Dear Ilya,
Am 25.06.2015 um 14:07 schrieb Ilya Dryomov:
On Wed, Jun 24, 2015 at 10:29 PM, Stefan Priebe wrote:
Am 24.06.2015 um 19:53 schrieb Ilya Dryomov:
On Wed, Jun 24, 2015 at 8:38 PM, Stefan Priebe
wrote:
Am 24.06.2015 um 16:55 schrieb Nick Fisk:
That kernel probably has the bug
Sounds good, thanks for the info and will wait and test with next releases.
> On Jun 27, 2015, at 9:24 AM, Nick Fisk wrote:
>
> Hi Reid,
>
> Yes they will, but if the object which the user is writing to (Disk Block if
> using RBD, which then maps to an object) has never been written to bef
On Sat, Jun 27, 2015 at 6:20 PM, Stefan Priebe wrote:
> Dear Ilya,
>
> Am 25.06.2015 um 14:07 schrieb Ilya Dryomov:
>>
>> On Wed, Jun 24, 2015 at 10:29 PM, Stefan Priebe
>> wrote:
>>>
>>>
>>> Am 24.06.2015 um 19:53 schrieb Ilya Dryomov:
On Wed, Jun 24, 2015 at 8:38 PM, Stefan Prieb
The current network design in Ceph
(http://ceph.com/docs/master/rados/configuration/network-config-ref)
uses nonredundant networks for both cluster and public communication.
Ideally, in a high load environment these will be 10 or 40+ GbE
networks. For cost reasons, most such installation will use
Hi Alex,
I think the answer is you do 1 of 2 things. You either design your network
so that it is fault tolerant in every way so that network interruption is
not possible. Or go with non-redundant networking, but design your crush map
around the failure domains of the network.
I'm interested in y
Hello everyone,
I created a bootable volume on openstack and trying to boot a ubuntu-server
14.04 image . I am able to get to the initial setup screen of Ubuntu, but
after asking for the timezone and location I am not able to proceed further as
it says it's not able to access the CDrom drive
Hi Nick,
Thank you fro writing back:
> I think the answer is you do 1 of 2 things. You either design your network
> so that it is fault tolerant in every way so that network interruption is
> not possible. Or go with non-redundant networking, but design your crush map
> around the failure domains
> -Original Message-
> From: Alex Gorbachev [mailto:a...@iss-integration.com]
> Sent: 27 June 2015 21:55
> To: Nick Fisk
> Cc: ceph-users@lists.ceph.com
> Subject: Re: [ceph-users] Redundant networks in Ceph
>
> Hi Nick,
>
> Thank you fro writing back:
>
> > I think the answer is you
Dear Ceph Community,
We are trying to integrate Ceph with OpenStack, and facing certificate issues
when attaching a Cinder volume to a Nova vm. We have the environment variable
OS_CACERT set to the correct certificate address, which is read to set cacert.
The certificate is verified successful
11 matches
Mail list logo