[ceph-users] Re: Pacific bluestore_volume_selection_policy

Hi Reed, no much sense to attach the logs to the mentioned tickets - the problem with the assertion is well-known and has been already fixed. Your current issue is weird config update behavior which prevents from applying the work around. Feel free to open ticket about that but I don't

[ceph-users] Re: Pacific bluestore_volume_selection_policy

Hi Igor, That’s correct (shown below). Would it be helpful for me to add logs/uploaded crash UUID’s to 53906 , 53907 , 54209 , 62928 ,

[ceph-users] Re: Pacific bluestore_volume_selection_policy

Hi Reed, it looks to me like your settings aren't effective. You might want to check OSD log rather than crash info and see the assertion's backtrace. Does it mention RocksDBBlueFSVolumeSelector as the one in https://tracker.ceph.com/issues/53906: ceph version 17.0.0-10229-g7e035110

[ceph-users] Re: Pacific bluestore_volume_selection_policy

Well, sadly, that setting doesn’t seem to resolve the issue. I set the value in ceph.conf for the OSDs with small WAL/DB devices that keep running into the issue, > $ ceph tell osd.12 config show | grep bluestore_volume_selection_policy > "bluestore_volume_selection_policy":

[ceph-users] Re: Pacific bluestore_volume_selection_policy

I ended up setting it in ceph.conf which appears to have worked (as far as I can tell). > [osd] > bluestore_volume_selection_policy = rocksdb_original > $ ceph config show osd.0 | grep bluestore_volume_selection_policy > bluestore_volume_selection_policy rocksdb_original

[ceph-users] Re: Pacific bluestore_volume_selection_policy

Hi, I just did the same in my lab environment and the config got applied to the daemon after a restart: pacific:~ # ceph tell osd.0 config show | grep bluestore_volume_selection_policy "bluestore_volume_selection_policy": "rocksdb_original", This is also a (tiny single-node) cluster