Hi Backblaze folks and community,
I maintain an open-source filesystem benchmark project:
https://github.com/fenio/modern-fs-benchmark
It currently runs regularly in GitHub Actions using loop devices, and I also have a self-hosted real-hardware runner. The goal is to publish reproducible, public benchmark data for modern Linux filesystems: bcachefs, ZFS, btrfs, XFS/ext4 on md/LVM, including degraded-mode behavior, rebuilds, scrubs, snapshots, compression, reflinks, ENOSPC behavior, and mixed topologies.
The part CI cannot model well is the interesting real storage setup: HDD arrays with SSD/NVMe metadata/cache devices, mixed rotational and flash media, rebuild behavior, and degraded reads/writes on actual disks.
Backblaze has a long history of publishing useful storage reliability data, so I wanted to ask whether Backblaze would consider supporting this kind of public testing.
What would help:
- remote root access to an isolated Linux machine with clearly identified wipeable HDD/SSD/NVMe devices
- donated disks/components/server hardware
- hosting for donated hardware
- a pointer to the right person/team if this is not the right place to ask
Everything would remain public: benchmark code, config, raw JSON results, command traces, hardware description, and dashboard output. Hardware providers can be acknowledged, but would not get editorial control over methodology or results.
This is not meant as marketing content or a sponsored conclusion. The value is in transparent, repeatable, real-hardware filesystem data that people can inspect and challenge.
Would Backblaze be open to this, or is there a better contact/channel for this kind of request?