Re: Snaptrim issue after nautilus to octopus upgrade

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

 



This is very important knowledge, thank you for sharing it.
I update Octopus to move Quincy step by step but I am stuck here because of
the snaptrim issue.
When I solve the issue I will prepare a new image and will continue to
upgrade to Quincy.

May I learn how fast I should be ?



Boris <bb@xxxxxxxxx>, 23 Ağu 2024 Cum, 19:11 tarihinde şunu yazdı:

> Ah crap, I didn't reply to the list :D
>
> tldr for the rest of the list:
> move to next release because of bad bug
> https://tracker.ceph.com/issues/53729#note-65
>
> I would go to pacific and then wait some time so the pglog_dups get
> cleaned up.
> Pacific and quincy are really nice releases that worked very well for us.
>
>
>
> Am Fr., 23. Aug. 2024 um 18:08 Uhr schrieb Özkan Göksu <
> ozkangksu@xxxxxxxxx>:
>
>> Hello Boris. Thank you so much for the recommendation.
>>
>> Actually my intention is jumping next releases until I reach Quincy.
>> What do you think about this? Am I gonna face with any problem while
>> jumping Octopus to Pacific and Quincy after ?
>>
>> Best regards.
>>
>> Boris <bb@xxxxxxxxx>, 23 Ağu 2024 Cum, 18:56 tarihinde şunu yazdı:
>>
>>> Hi, I would suggest to move fast to the next release.
>>> There was a bug that still haunts my sleep that is known as the
>>> PGLOG_DUP bug.
>>>
>>> You can check if you are suffering from it here:
>>> https://tracker.ceph.com/issues/53729#note-65
>>>
>>> Basically the pglog dups would not be cleaned anymore. And snaptrim
>>> seems to trigger that. The pacific release got the fix.
>>>
>>> Cheers
>>>  Boris
>>>
>>> Am Fr., 23. Aug. 2024 um 16:48 Uhr schrieb Özkan Göksu <
>>> ozkangksu@xxxxxxxxx>:
>>>
>>>> Hello folks.
>>>>
>>>> We have a ceph cluster and we have 2000+ RBD drives on 20 nodes.
>>>>
>>>> We upgraded the cluster from 14.2.16 to 15.2.14 and after the upgrade we
>>>> started to see snap trim issues.
>>>> Without the "nosnaptrim" flag, the system is not usable right now.
>>>>
>>>> I think the problem is because of the omap conversion at Octopus
>>>> upgrade.
>>>>
>>>> Note that the first time each OSD starts, it will do a format
>>>> conversion to
>>>> improve the accounting for “omap” data. This may take a few minutes to
>>>> as
>>>> much as a few hours (for an HDD with lots of omap data). You can disable
>>>> this automatic conversion with:
>>>>
>>>> What should I do to solve this problem?
>>>>
>>>> Thanks.
>>>> _______________________________________________
>>>> ceph-users mailing list -- ceph-users@xxxxxxx
>>>> To unsubscribe send an email to ceph-users-leave@xxxxxxx
>>>>
>>>
>>>
>>> --
>>> Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im
>>> groüen Saal.
>>>
>>
>
> --
> Die Selbsthilfegruppe "UTF-8-Probleme" trifft sich diesmal abweichend im
> groüen Saal.
>
_______________________________________________
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