3 ms·
Dunno, man. It's an old Mac-mini, single disk (the SSD is explicitly called out) fairly obviously used for private stuff. You can wring it. In a production e
by guenthert 2y ago
Dunno, man. It's an old Mac-mini, single disk (the SSD is explicitly called out) fairly obviously used for private stuff. You can wring it.
In a production environment you cut you losses and restore from back-up. No-one wants to deal with half-baked recovery operations which might or might not yield a consistent state with (a little) less, but unknown, data loss.
- bravetraveler 2y agoIt's not lost on me that this is a low stakes situation, they had backups and could afford being artful in their process. That's what makes this wheel-spinning so confounding.
- abofh 2y agoI don't think this was wheel-spinning so much as yarn-pulling, finding interesting tid-bits and seeing where they go. The most interesting things (to me) are when something doesn't quite line up with expectations, and then digging until I understand what the difference was - usually I misunderstood something (or failed to recall something, like in this case, disk/filesystem caches) - and I find myself more enlightend. I totally get doing this to learn because it was an interesting process. But yea, if this were for money? I'd just restore from backups and follow the SOP - because for money, the _why_ something failed is often unimportant, the remedy is the same -- reboot, replace, correlate, correct.
- bravetraveler 2y agoPlaying with Schrodinger's stuff. The storage industry/equipment lies so pervasively, even when it's working as intended More importantly, perhaps, is this is a "brain worm" being spread to others. Not to armchair too much, but there's a certain responsibility by publishing your writing. I'd hope for more dutiful research before publishing/risking data with anything even remotely nearing suggestion. Loud/clear warnings. We're all playing the Telephone Game whether we want to or not.