yep, as long as its skippable just like the vacuum is.
Such semi-transient events are hard to graps, or detect.
A Hard-crash during disk-IO just plain sucks.
I’d assume the only means of detecting are some time-constraints during DB scan/read.
Stuff like this shouldnt be happening on a journaled (ext3) fs though, afaik. I deffo wouldnt like the mt-daapd startup even further delayed on my slug.
Yeah, but if the first thing I try to do with the database gives me an error, I can always just move the db out of the way and make a new one. that would be relatively painless and easy.