Hi,
also i'm getting these errors only for pre jewel images:
2017-05-06 03:20:50.830626 7f7876a64700 -1
librbd::object_map::InvalidateRequest: 0x7f7860004410 invalidating
object map in-memory
2017-05-06 03:20:50.830634 7f7876a64700 -1
librbd::object_map::InvalidateRequest: 0x7f7860004410 invalida
Hi,
On 06-05-17 20:08, Wido den Hollander wrote:
>> Op 6 mei 2017 om 9:55 schreef Christian Balzer :
>>
>>
>>
>> Hello,
>>
>> On Sat, 6 May 2017 09:25:15 +0200 (CEST) Wido den Hollander wrote:
>>
Op 5 mei 2017 om 10:33 schreef Sam Wouters :
Hi,
we have a small cluste
> Op 6 mei 2017 om 20:00 schreef Peter Maloney
> :
>
>
> I was testing ceph in a centos 7 VM, just so I could support someone
> that wants to use CentOS 7, and I ran into a problem... What am I doing
> wrong?
>
> First I tried just without any ipv6 changes, and the eth0 had an ipv6
> address,
> Op 6 mei 2017 om 9:55 schreef Christian Balzer :
>
>
>
> Hello,
>
> On Sat, 6 May 2017 09:25:15 +0200 (CEST) Wido den Hollander wrote:
>
> > > Op 5 mei 2017 om 10:33 schreef Sam Wouters :
> > >
> > >
> > > Hi,
> > >
> > > we have a small cluster running on jewel 10.2.7; NL-SAS disks only
I was testing ceph in a centos 7 VM, just so I could support someone
that wants to use CentOS 7, and I ran into a problem... What am I doing
wrong?
First I tried just without any ipv6 changes, and the eth0 had an ipv6
address, but it still didn't work. I think it looked the same but didn't
save th
Hi all,
I have a 3 nodes CEPH cluster, each node with 4 OSD and 1 monitor and
replication across hosts defined in the crushmap. 2 pools (1 size=3, min-size=2
, 1 size=2 min-size 2)
One of the nodes failed (hardware failure) so I removed it from the crush map
and change replication from host
Hello,
On Sat, 6 May 2017 09:25:15 +0200 (CEST) Wido den Hollander wrote:
> > Op 5 mei 2017 om 10:33 schreef Sam Wouters :
> >
> >
> > Hi,
> >
> > we have a small cluster running on jewel 10.2.7; NL-SAS disks only, osd
> > data and journal co located on the disks; main purpose rgw secondary z
> Op 5 mei 2017 om 21:51 schreef Yehuda Sadeh-Weinraub :
>
>
> RGW has supported since forever. Originally it was the only supported
> frontend, and nowadays it is the least preferred one.
>
> Rgw was first developed over fastcgi + lighttpd, but there were some
> issues with this setup, so we s
> Op 5 mei 2017 om 10:33 schreef Sam Wouters :
>
>
> Hi,
>
> we have a small cluster running on jewel 10.2.7; NL-SAS disks only, osd
> data and journal co located on the disks; main purpose rgw secondary zone.
>
> Since the upgrade to jewel, whenever a deep scrub starts on one of the
> rgw ind