Open Zizhao-Wang opened 8 months ago
I think the default target file size ended up fragmenting the zones and causing the issue. This can happen with the fillseq workload which skips the normal write flow.
I suggest you set --target_file_size_base=$(( 1000 1024 1024 ))
There is a script in the zenfs tests directory called get_good_db_bench_params_for_zenfs.sh , this will generate a decent set of parameters for your device geometry.
Issue Description I encountered an issue while conducting a large-scale data write test using ZenFS with RocksDB. The test failed after writing around 200 million entries, with an error message “IO error: No space left on device: Zone allocation failure”.
Environment Setup
Steps to Reproduce
../rocksdb/plugin/zenfs/util/zenfs mkfs\ --zbd=nvme0n1 \ --force \ --aux_path=/root/logs
Expected vs. Actual Results
Expected vs. Actual Results
Additional Information
Any insights or assistance in addressing this issue would be greatly appreciated.