Re: Determine effective min_alloc_size for a specific OSD

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

 



Bluestore alloc size is fixed in config and used only at bluestore OSD creation. You can change it on conf and then recreate your OSD.


k

On 02.12.2020 14:51, 胡 玮文 wrote:
I remember that min_alloc_size cannot be changed after OSD creation, but I can’t find the source now. Searching results in this PR[1], which state: “min_alloc_size is now fixed at mkfs time”. Is it true that we can only change the min_alloc_size by destroying and recreating the OSD?

If it is true, then all the provided methods does not give real effective min_alloc_size. Assuming min_alloc_size cannot be changed can’t be changed without OSD recreation:
* Output of “ceph daemon osd.0 config ...” shows old value (64k), but after I restart the OSD daemon, it shows new value (32k), which can’t be correct.
* Output of “ceph config get ...” always shows new value, which can’t be the effective value.

Or maybe my knowledge is out of date. Now we can really change the min_alloc_size by just setting the new value and restarting the OSD daemon?
_______________________________________________
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