61–70 of 261 posts
Misleading headline since after testing eight more drives, none more failed. 2/12 is not nearly as dramatic as “half”, and the ones that lost data are the cheap brands as one would expect.
You can either not editorialize the title, and accept that the thread contains updates, or editorialize it and violate HN guidelines. Either choice will lead somebody to complain
There is a flood of fake SSDs currently, mostly big brands. I've recently purchased counterfeit 1TB. It passes all the tests, performance is ok, it works... except it gets episodes where ioping would be anything between 0.7 ms and 15 seconds, that is under zero load. And these are quality fakes from a physical appearance perspective. The only way I could tell mine was fake is that the official Kingston firmware updat…
We shipped a shader cache in the latest release of OBS and quickly had reports come in that the cached data was invalid. After investigating, the cache files were the correct size on disk but the contents were all zero. On a journaled file system this seems like it should be impossible, so the current guess is that some users have SSDs that are ignoring flushes and experience data corruption on crash / power loss.
I think the last time I had corrupted files after a power loss was in a FAT32 disk on Win98, but you'd usually get garbage data, not all zeros.
If you need PLP use an enterprise drive. That's what they're for.
Earlier quoted context omitted.
There were a few more listed deeper in the thread. Fyi, the nitter version is actually readable: https://nitter.net/xenadu02/status/1495693475584557056#m Samsung 970 Evo Plus: MZ-V7S2T0, 2021.10: Pass WD Red: WDS100T1R0C-68BDK0, 04Sept2021: Pass Crucial P2 250GB CT250P2SSD8, FW P2CR046: Pass Samsung 980 250GB MZ-V8V250, 2021/11/07: Pass WD Black SN750 1TB WDS100T1B0E, 09Jan2022: Pass WD Green SN350 240GB WDS240G20C,…
So...vendors no sane person would store valuable data on their drives were the only ones that failed. The sound of a dog biting a man...
We shipped a shader cache in the latest release of OBS and quickly had reports come in that the cached data was invalid. After investigating, the cache files were the correct size on disk but the contents were all zero. On a journaled file system this seems like it should be impossible, so the current guess is that some users have SSDs that are ignoring flushes and experience data corruption on crash / power loss.
Depending on mount options, ext4fs does metadata journaling ensuring the FS itself is not borked, but not data journaling which would safeguard the file contents in event of unclean shutdown with pending writes in the caches.
The same phenomenon is at play when people complain that their log files contain NUL bytes after a crash. The file system metadata has been updated for the size of the file to fit the appended write, but the data itself was not written out yet.
We shipped a shader cache in the latest release of OBS and quickly had reports come in that the cached data was invalid. After investigating, the cache files were the correct size on disk but the contents were all zero. On a journaled file system this seems like it should be impossible, so the current guess is that some users have SSDs that are ignoring flushes and experience data corruption on crash / power loss.
I had this exact experience with my workstation SSD (NTFS) after a short power loss while NPM was running. After I turned the computer back on, several files (package.json, package-lock.json and many others inside node_modules) had the correct size on disk but were filled with zeros. I think the last time I had corrupted files after a power loss was in a FAT32 disk on Win98, but you'd usually get garbage data, not al…
Misleading headline since after testing eight more drives, none more failed. 2/12 is not nearly as dramatic as “half”, and the ones that lost data are the cheap brands as one would expect.
You can either not editorialize the title, and accept that the thread contains updates, or editorialize it and violate HN guidelines. Either choice will lead somebody to complain
Specifically: use the original title, then express your view as a top level comment. If people agree with it, the comment is naturally voted up.
Earlier quoted context omitted.
You can either not editorialize the title, and accept that the thread contains updates, or editorialize it and violate HN guidelines. Either choice will lead somebody to complain
It's clear from the guidelines: https://news.ycombinator.com/item?id=38365934#38368867 Specifically: use the original title, then express your view as a top level comment. If people agree with it, the comment is naturally voted up.
Admittedly this is a twitter thread, so no "actual title" exists.
Earlier quoted context omitted.
You can either not editorialize the title, and accept that the thread contains updates, or editorialize it and violate HN guidelines. Either choice will lead somebody to complain
Clearly they should only editorialize the ones that are wrong.