Comment 4 for bug 1815305

I do see a reference to orphan inode in /var/log/boot.log -- although the entries don't have timestamps so it's hard to know when it happened. But this is decent evidence toward that theory.

But more interestingly, damage to the middle or audio data doesn't seem to indicate mixxx as being the cause -- writing metadata should cause some sort of problem at the ends of the files, right?

I'm going to keep this feature off for now because I have a gig coming up, but I will turn it back on and watch out for this. I also haven't had any problems with mixxx writing data recently, so if I can't reproduce after a while I'll close the bug. Thanks for the ideas!