Re: 1 bogus remapped PG (stuck pg_temp) -- how to cleanup?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Thanks!

PG split solved this problem for us too


k
Sent from my iPhone

> On 2 Feb 2022, at 17:11, Burkhard Linke <Burkhard.Linke@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
> 
> Hi,
> 
> 
> I've found a solution for getting rid of the stale pg_temp. I've scaled the pool up to 128 PGs (thus "covering" the pg_temp). Afterwards the remapped PG was gone. I'm currently scaling down back to 32, no extra PG (either regular or temp) so far.
> 
> 
> The pool is almost empty, so playing around with PG numbers is not a problem in our case.
> 
> 
> Regards,
> 
> Burkhard
> 
> 
> _______________________________________________
> ceph-users mailing list -- ceph-users@xxxxxxx
> To unsubscribe send an email to ceph-users-leave@xxxxxxx

_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux