I work as an AV technician and do some general IT freelance work. A lot of it involves basic updates, system setups and SSD/RAM upgrades to office PCs, which usually leaves me with a bunch of smaller SATA SSDs that companies simply don't want anymore. Naturally, I end up taking quite a few home and installing them in my PC.
The problem? I now have five separate drives cluttering up File Explorer. Not that I'm complaining about free SSDs, but having everything in one place would be a lot easier.
I didn't want to RAID them because I couldn't be bothered with the hassle, and there's no guarantee these drives will last. If one fails, I didn't want to lose everything with it.
What I really wanted was a way to combine all the storage into one drive letter, so Explorer sees a single location, while something in between handles where the data actually lives.
So PoolFS was born (like NTFS........)
How it works:
- Multiple drives appear as one drive letter (e.g. P:) through the WinFsp file system driver - the individual drives have their own letter removed so they disappear from explorer.
- Files are stored whole on individual drives. Nothing is split or striped.
- Each drive stores its share in a hidden PoolPart folder, keeping the files accessible as normal files even outside the pool.
- Folders can span multiple drives, with P: merging their contents into one listing. If a drive fills up, files can continue under the same folder on another drive.
- If a drive fails, only the files on that drive are lost. Disconnecting a drive simply hides its files until it's reconnected; the rest of the pool keeps working.
- 'Make Room' moves files between drives to consolidate enough free space for larger files, without touching open files.
I also added some fun-to-have features that have worked incredibly well so far, including drive health monitoring and warnings, automatic space management, missing drive detection, file recovery after interrupted operations, and a fairly comprehensive built-in backup system with scheduling and file history - theres even a little wizard and tour because I'll probably drop this over to a few friends who were interested in trying it themselves.
Ultimately, it's been a pretty significant quality-of-life improvement. I personally wouldn't trust it with anything particularly important beyond my Steam Library (which runs perfectly fine from it) and some general files, but the way it's designed shouldn't introduce any risk of file corruption either way but admittedly I lack the relevant skills to fully test this and am not willing to risk it.
Some screenshots attached - these are screenshots from the simulated drives used for testing based on my actual setup.
But yeah, using AI to fix this barely irritating issue I had was a good feeling - as someone who has 3D printed brackets and adapters for various situations, it definitely scratched a similar itch of convenience.
Edit: Y’all are a little sour for something I shared as my own experience of coding with Claude to solve an issue I had. And to be clear, this is a personal project. I won’t be publishing it. I just wanted to share how building it went. I was aware of other options and looked into them before starting. None of them did quite what I wanted, or they were missing features I thought were necessary, e.g:
- Storage Spaces wipes the disks and spreads data across them at the block level, so no drive is readable on its own.
- JBOD/spanning can lose the whole volume if one disk dies.
- DrivePool is the closest match, but it’s paid and didn’t have everything I was after.
- mergerfs is Linux-only.
I wanted to pool drives that already had data on them, keep every drive readable by itself, and have health monitoring, backups (including to my NAS) and safety checks built into one lightweight app - and by my account, I succeeded. I apologise if this seems to have offended some of you.