I have a hobby project that’s grown up into something that might might be of interest to tinkerers in this community.
It’s an app that scans file systems (portions that you identify) repeatedly over time. It identifies changes at the file system level but also uses a hash-based strategy to detect potential bit rot. It can “validate” some types of files. It does quite a bit and if you’re remotely interested, I invite you to give it a look.
The backend is in Rust, the frontend is in React/TypeScript. It’s open source. Docker containers are available at docker hub, binaries can be downloaded from github or crates.io via cargo.
Thanks Gregg this looks like a very interesting project for the many collectors of extremely large libraries in this community.
I look forward to trying it out and giving you some feedback on this project, even though compared to many here my library is of modest size
Running it now Gregg and doing an initial first scan, I think it will be helpful in tracking new additions and metadata and image changes as I have been doing a lot as part of the library improvement process.
It certainly looks like it can be a good additional tool to anyone with a large library that want’s to understand changes over time.
I have been using SyncbackPro to copy the files to my Roon Linux server for many years, but it has limited capacity for reporting on changes beyond the last few scan so this could be very useful, especially if I set up a daily/weekly schedule to scan my music library.
At the moment I am testing it on my Ripping and Metadata editing Windows PC, but I think long term running the Linux version on my DietPi Server would make the most sense as that is always running. The Web UI should work nicely in that case, as I should hopefully be able to run it and monitor it from my PC, laptop or tablet.
Personally, I think Docker is the way to run this and hopefully the images on docker hub are helpful to people. I run it in as a Docker container on TrueNAS using those images.
Just to add some additional information on this project from a very recent personal experience with FsPulse.
I downloaded and ran the latest version of FsPulse on my Windows PC after @gTunes post. I was quite shocked by the number of alerts created and set around fixing them. The majority of alerts were related to Qobuz purchases incorrectly naming the image files as png when they were jpg format, so were easily fixed.
More importantly it did find around 16 corrupt Flac files in my library (on just shy of 80K tracks) which I didn’t believe at first. Upon playback listening and testing with dbPoweramp the corruption was confirmed and I set about replacing them. All my backup’s from the last two years were also corrupt, so I resorted to CD:s and some friends. I now have a fully clean library and FsPulse has been installed on my Linux based Roon server to run weekly scans, which will hopefully be mostly about fixing any new Qobuz purchases I forget to rename the image files on (if they are still being sent down incorrectly as that could be an old issue).
Anyway a big thank you to @gTunes for creating such a useful free tool and a recommendation for more of you to try this easy to install and use tool that makes keeping your large music library working well easier.
