<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hesela analyses: new and updated</title><link>https://hesela.com/</link><description>Editorial dates for storage analyses published by Hesela team.</description><language>en</language><atom:link href="https://hesela.com/rss.xml" rel="self" type="application/rss+xml"/><item><title>3D NAND retention: layer count is not a reliability rating</title><link>https://hesela.com/analyses/3d-nand-retention-evidence/</link><guid isPermaLink="false">https://hesela.com/analyses/3d-nand-retention-evidence/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Separate NAND architecture, dwell, thermal annealing and read conditions before interpreting raw error rates or claims of restored SSD endurance.</description></item>
<item><title>AFR is a rate, not a one-year failure probability</title><link>https://hesela.com/analyses/afr-rate-not-probability/</link><guid isPermaLink="false">https://hesela.com/analyses/afr-rate-not-probability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Why exposure, zero-failure probability bounds, survival curves and censoring assumptions matter when interpreting drive reliability, with reproducible synthetic examples.</description></item>
<item><title>Atomic rename is not a durable commit</title><link>https://hesela.com/analyses/atomic-rename-directory-durability/</link><guid isPermaLink="false">https://hesela.com/analyses/atomic-rename-directory-durability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>File contents, directory entries and commit acknowledgements have different persistence boundaries. Linux documentation and two USENIX studies explain what a rename does not guarantee.</description></item>
<item><title>Backup verification is not a restore test</title><link>https://hesela.com/analyses/backup-verification-is-not-a-restore-test/</link><guid isPermaLink="false">https://hesela.com/analyses/backup-verification-is-not-a-restore-test/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Separate backup completion, integrity, freshness and usable recovery, with reproducible SQLite and rsync experiments and explicit limits.</description></item>
<item><title>Bloom filters: optimize the lookup, not each filter</title><link>https://hesela.com/analyses/bloom-filters-lsm-read-cost/</link><guid isPermaLink="false">https://hesela.com/analyses/bloom-filters-lsm-read-cost/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>LSM lookup costs, filter retention and counting limits, with reproducible allocation, deletion and memory examples grounded in primary sources.</description></item>
<item><title>Why a valid checksum can still return the wrong data</title><link>https://hesela.com/analyses/checksums-identity-and-lost-writes/</link><guid isPermaLink="false">https://hesela.com/analyses/checksums-identity-and-lost-writes/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Checksums, identity, freshness, Linux verity and disk encryption: what successful verification does and does not prove, with reproducible examples.</description></item>
<item><title>eMMC, UFS and RPMB: interface, boot and security boundaries</title><link>https://hesela.com/analyses/emmc-ufs-rpmb-boundaries/</link><guid isPermaLink="false">https://hesela.com/analyses/emmc-ufs-rpmb-boundaries/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>How managed flash differs from raw NAND, why eMMC and UFS are not interchangeable interfaces, and why RPMB authentication is neither encryption nor a backup.</description></item>
<item><title>Ext4 journal replay: why old writes must sometimes be skipped</title><link>https://hesela.com/analyses/ext4-journal-replay-revocation/</link><guid isPermaLink="false">https://hesela.com/analyses/ext4-journal-replay-revocation/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>JBD2 replay, checksum failure paths and ambiguous log tails, with source-checked recovery boundaries and reproducible counterexamples.</description></item>
<item><title>Why retrying a failed fsync does not prove durability</title><link>https://hesela.com/analyses/fsync-failure-retry-durability/</link><guid isPermaLink="false">https://hesela.com/analyses/fsync-failure-retry-durability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Why a successful fsync retry can leave stale data: historical research, Linux close errors, POSIX portability, synchronization boundaries and reproducible descriptor-lifetime observations.</description></item>
<item><title>io_uring: completion is not a durable commit</title><link>https://hesela.com/analyses/io-uring-completion-ordering-durability/</link><guid isPermaLink="false">https://hesela.com/analyses/io-uring-completion-ordering-durability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>io_uring write ordering, protection information, cancellation CQEs and linked timeouts: what each result proves, and what still needs synchronization.</description></item>
<item><title>iSCSI identity, sessions and recovery: what a second portal does not prove</title><link>https://hesela.com/analyses/iscsi-identity-sessions-recovery/</link><guid isPermaLink="false">https://hesela.com/analyses/iscsi-identity-sessions-recovery/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Separate iSCSI names, portals, sessions, command ordering and recovery levels, with a source-checked distinction between projected and measured performance.</description></item>
<item><title>Magnetic retention: why 60 kBT is not an expiry date</title><link>https://hesela.com/analyses/magnetic-retention-time-and-probability/</link><guid isPermaLink="false">https://hesela.com/analyses/magnetic-retention-time-and-probability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>A reproducible two-state model separates first reversal, final-state error and magnetization decay, and shows why a mean energy barrier cannot predict retention.</description></item>
<item><title>Disk failure prediction: signals, scores and alert costs</title><link>https://hesela.com/analyses/ml-disk-failure-prediction/</link><guid isPermaLink="false">https://hesela.com/analyses/ml-disk-failure-prediction/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Lu et al.&apos;s fleet study tested SMART, performance and location signals. Interpret its scores alongside explicit alert denominators, prevalence and validation limits.</description></item>
<item><title>Memory-mapped files: visibility, size and synchronization</title><link>https://hesela.com/analyses/mmap-visibility-size-durability/</link><guid isPermaLink="false">https://hesela.com/analyses/mmap-visibility-size-durability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Seven reproducible Linux checks distinguish mapped visibility, file size, partial-page tails, SIGBUS and sync argument errors from power-loss durability.</description></item>
<item><title>NFS stable writes: what COMMIT, flush and FUA actually promise</title><link>https://hesela.com/analyses/nfs-stable-writes-flush-fua/</link><guid isPermaLink="false">https://hesela.com/analyses/nfs-stable-writes-flush-fua/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>NFSv3 stability, COMMIT verifiers and Linux flush/FUA: distinguish durable writes from cache visibility, with bounded NFSv4 delegation comparisons.</description></item>
<item><title>NVMe over Fabrics: transports, discovery and security boundaries</title><link>https://hesela.com/analyses/nvme-fabrics-transports-discovery/</link><guid isPermaLink="false">https://hesela.com/analyses/nvme-fabrics-transports-discovery/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Distinguish NVMe/TCP, NVMe/RDMA and NVMe/FC from discovery, path selection and security, without treating a transport label as a performance guarantee.</description></item>
<item><title>O_DIRECT alignment: query the file, not a fixed block size</title><link>https://hesela.com/analyses/o-direct-alignment-by-kernel/</link><guid isPermaLink="false">https://hesela.com/analyses/o-direct-alignment-by-kernel/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Query O_DIRECT per-file alignment and distinguish cache hints, prefetch, NOWAIT and mincore residency from actual I/O and durable writes.</description></item>
<item><title>Phi failure detectors: suspicion is not a failure probability</title><link>https://hesela.com/analyses/phi-failure-detectors-suspicion/</link><guid isPermaLink="false">https://hesela.com/analyses/phi-failure-detectors-suspicion/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>What a phi score measures, why Cassandra&apos;s score differs from the original model, and why suspecting a replica does not fence it. Includes reproducible synthetic examples.</description></item>
<item><title>Protection information: when success skips the checksum</title><link>https://hesela.com/analyses/protection-information-escape-tags/</link><guid isPermaLink="false">https://hesela.com/analyses/protection-information-escape-tags/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>A pinned Linux verifier test separates PI escape tags, guard checks and 32-bit reference aliases. Sixteen cases show why accepted does not always mean checked.</description></item>
<item><title>RocksDB: a WAL sync is not a memtable flush</title><link>https://hesela.com/analyses/rocksdb-wal-flush-manifest-boundaries/</link><guid isPermaLink="false">https://hesela.com/analyses/rocksdb-wal-flush-manifest-boundaries/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>RocksDB WAL sync, memtable flush, write stalls, read snapshots, checkpoints and backups have distinct recovery and retention contracts.</description></item>
<item><title>Disk scrubbing: detection time is not a durability guarantee</title><link>https://hesela.com/analyses/scrubbing-detection-not-durability/</link><guid isPermaLink="false">https://hesela.com/analyses/scrubbing-detection-not-durability/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>How scrub coverage and irregular inspection intervals limit detection evidence, with exact reproducible examples of waiting-time bias.</description></item>
<item><title>SIEVE cache eviction: one bit is not scan resistance</title><link>https://hesela.com/analyses/sieve-cache-eviction-traces/</link><guid isPermaLink="false">https://hesela.com/analyses/sieve-cache-eviction-traces/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Explain SIEVE versus CLOCK and LRU, replay cache traces and FIFO capacity anomalies, and separate miss counts from storage performance claims.</description></item>
<item><title>Sleeping disks: one readable block is not a recoverable array</title><link>https://hesela.com/analyses/sleeping-disks-partial-reconstruction/</link><guid isPermaLink="false">https://hesela.com/analyses/sleeping-disks-partial-reconstruction/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>An exhaustive check of two historical XOR codes separates serving a read without spin-up from recovering every data symbol. Includes code, all 512 availability states and explicit limits.</description></item>
<item><title>Snapshots and backups: which failures can you recover from?</title><link>https://hesela.com/analyses/snapshot-backup-recovery-boundaries/</link><guid isPermaLink="false">https://hesela.com/analyses/snapshot-backup-recovery-boundaries/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Separate snapshot consistency, independent recovery copies and RPO/RTO targets, with source-backed OpenZFS, PostgreSQL and VSS examples.</description></item>
<item><title>Sparse files, preallocation and thin-pool capacity</title><link>https://hesela.com/analyses/sparse-files-preallocation-thin-capacity/</link><guid isPermaLink="false">https://hesela.com/analyses/sparse-files-preallocation-thin-capacity/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>File size, allocated blocks and thin-pool headroom are different measurements. Learn what preallocation, hole punching and zero-filled reads actually establish.</description></item>
<item><title>SSD wear indicators: estimates, failure evidence and NVMe scope</title><link>https://hesela.com/analyses/ssd-wear-out-failure-signatures/</link><guid isPermaLink="false">https://hesela.com/analyses/ssd-wear-out-failure-signatures/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Percentage Used estimates consumed endurance; it is not a failure probability. Available Spare measures a different quantity, and a read-only warning is not a promise of continued data access. Historical SATA failures and Google&apos;s field study illustrate these limits, but neither calibrates modern NVMe warning coverage. Keep device identity, log identifier and counter scope with every observation.</description></item>
<item><title>Slow RAID hours are not request tail latency</title><link>https://hesela.com/analyses/storage-tail-slowdowns-raid-fanout/</link><guid isPermaLink="false">https://hesela.com/analyses/storage-tail-slowdowns-raid-fanout/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>Slow-drive hours and request percentiles count different events. Source review and exact examples distinguish fan-out, hedged reads, cancellation work and replica dependence.</description></item>
<item><title>Unnamed files: publishing is not replacing</title><link>https://hesela.com/analyses/tmpfile-publication-rename-contracts/</link><guid isPermaLink="false">https://hesela.com/analyses/tmpfile-publication-rename-contracts/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>A native Linux observation separates O_TMPFILE staging, linkat publication, no-replace rename and atomic exchange from crash durability.</description></item>
<item><title>WAL, checkpoints and torn pages: three different recovery guarantees</title><link>https://hesela.com/analyses/wal-checkpoints-torn-pages/</link><guid isPermaLink="false">https://hesela.com/analyses/wal-checkpoints-torn-pages/#updated-2026-10-17</guid><pubDate>Sat, 17 Oct 2026 00:00:00 GMT</pubDate><description>WAL recovery boundaries: PostgreSQL hint-bit writes, page-image compression and statistics traps, plus InnoDB doublewrite and SQLite commit semantics.</description></item>
<item><title>B-epsilon trees: visible updates, deferred work</title><link>https://hesela.com/analyses/b-epsilon-trees-buffered-updates/</link><guid isPermaLink="false">https://hesela.com/analyses/b-epsilon-trees-buffered-updates/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>How buffered tree updates remain query-visible, why blind upserts differ from read-modify-write, and why equal flush counts can hide different completion times.</description></item>
<item><title>Missing SMART ages and the limits of drive-age comparisons</title><link>https://hesela.com/analyses/backblaze-age-missing-data-audit/</link><guid isPermaLink="false">https://hesela.com/analyses/backblaze-age-missing-data-audit/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>A full Q4 2025 raw-data audit finds 18 TB drives in a mislabeled capacity group and shows why excluding 106 missing-age drive-days also excludes 19 failures.</description></item>
<item><title>Content-defined chunking: boundaries are not identity</title><link>https://hesela.com/analyses/content-defined-chunking-boundaries/</link><guid isPermaLink="false">https://hesela.com/analyses/content-defined-chunking-boundaries/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Reproducible FastCDC examples show how file framing, parameter changes and terminal chunks alter measured reuse, even when file contents remain unchanged.</description></item>
<item><title>Crash-consistency tests: the oracle is part of the result</title><link>https://hesela.com/analyses/crash-testing-oracles-and-bounds/</link><guid isPermaLink="false">https://hesela.com/analyses/crash-testing-oracles-and-bounds/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>What ALICE, CrashMonkey/ACE, SQLite and Ananke actually test: fault boundaries, separate recovery outcomes and an executable correctness-oracle example.</description></item>
<item><title>Datacenter failure tickets are not failed-device counts</title><link>https://hesela.com/analyses/datacenter-hardware-failure-tickets/</link><guid isPermaLink="false">https://hesela.com/analyses/datacenter-hardware-failure-tickets/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>A hardware ticket, a failed device and a service outage are different counting units. Review the reported fleet figures, separate response time from repair time, and reproduce why a 120-second failure-burst rule need not limit a burst to 120 seconds.</description></item>
<item><title>Fast file clones: where the copying cost goes</title><link>https://hesela.com/analyses/file-clones-deferred-copy-cost/</link><guid isPermaLink="false">https://hesela.com/analyses/file-clones-deferred-copy-cost/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Separate reflinks, hard links and in-kernel copies; trace deferred costs, Btrfs maintenance, shared-space accounting and FAST 2020&apos;s research limits.</description></item>
<item><title>CMR is not refresh-free: adjacent-track interference in HDDs</title><link>https://hesela.com/analyses/hdd-adjacent-track-interference-refresh/</link><guid isPermaLink="false">https://hesela.com/analyses/hdd-adjacent-track-interference-refresh/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Repeated HDD writes can trigger protective refreshes even with CMR. Separate write-induced ATI, read-channel interference and SMR band rewrites before diagnosing latency.</description></item>
<item><title>HDD workload ratings: count reads, check the clock</title><link>https://hesela.com/analyses/hdd-annualized-workload-rate/</link><guid isPermaLink="false">https://hesela.com/analyses/hdd-annualized-workload-rate/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>An HDD workload rating is not SSD TBW or a failure countdown. Power-on hours, read traffic and maintenance scans change what the annualized number means.</description></item>
<item><title>HDD write verification: completion, persistence and comparison</title><link>https://hesela.com/analyses/hdd-write-verification-iraw/</link><guid isPermaLink="false">https://hesela.com/analyses/hdd-write-verification-iraw/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Read-after-write verification, IRAW and SCSI VERIFY answer different questions from flush or FUA. Learn what a successful check does and does not establish.</description></item>
<item><title>LMDB readers: a stable snapshot can exhaust a fixed map</title><link>https://hesela.com/analyses/lmdb-readers-page-reuse-map-full/</link><guid isPermaLink="false">https://hesela.com/analyses/lmdb-readers-page-reuse-map-full/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>A controlled LMDB experiment separates reader lifetime, reusable pages and map capacity: why a live reader can stop writes without holding the writer mutex.</description></item>
<item><title>Why deleted NFS files become .nfs files</title><link>https://hesela.com/analyses/nfs-silly-rename-open-unlink/</link><guid isPermaLink="false">https://hesela.com/analyses/nfs-silly-rename-open-unlink/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Silly rename, open-file preservation and a misleading Linux comment: trace NFS deletion from the 1985 paper to a pinned implementation and RFC erratum.</description></item>
<item><title>NVMe multipath: ANA access states and Linux path policies</title><link>https://hesela.com/analyses/nvme-multipath-ana-path-selection/</link><guid isPermaLink="false">https://hesela.com/analyses/nvme-multipath-ana-path-selection/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Separate NVMe namespace identity from ANA access states: NSID scope, identifier lifetime, Linux path policies and controller-level queue accounting.</description></item>
<item><title>Object ETags: checksums and conditional writes are different</title><link>https://hesela.com/analyses/object-etags-checksums-conditional-writes/</link><guid isPermaLink="false">https://hesela.com/analyses/object-etags-checksums-conditional-writes/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>S3 ETags, full-object and composite checksums, version IDs and write preconditions: what each validates, and how to avoid checking download metadata instead of bytes.</description></item>
<item><title>RAIDZ expansion: why old blocks keep their parity cost</title><link>https://hesela.com/analyses/raidz-expansion-parity-capacity/</link><guid isPermaLink="false">https://hesela.com/analyses/raidz-expansion-parity-capacity/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Reflow spreads old blocks across more disks without changing their data-to-parity ratio. A reproducible model separates retained parity overhead, reported space and snapshot-aware rewriting.</description></item>
<item><title>Replica repair: what has actually converged?</title><link>https://hesela.com/analyses/replica-repair-coverage/</link><guid isPermaLink="false">https://hesela.com/analyses/replica-repair-coverage/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Replica repair coverage, quorum overlap and set reconciliation: why matching keys, successful responses and compact summaries do not prove identical durable state.</description></item>
<item><title>Replication acknowledgements: received, durable, applied</title><link>https://hesela.com/analyses/replication-acknowledgements-durability-lag/</link><guid isPermaLink="false">https://hesela.com/analyses/replication-acknowledgements-durability-lag/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Compare replication acknowledgements, WAL retention and logical failover readiness; distinguish durable writes, replay and missing or unusable slots.</description></item>
<item><title>SQLite WAL checkpoint starvation: success is not completion</title><link>https://hesela.com/analyses/sqlite-wal-checkpoint-starvation/</link><guid isPermaLink="false">https://hesela.com/analyses/sqlite-wal-checkpoint-starvation/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Measured SQLite WAL checkpoints and stale-snapshot retries: why restarting a transaction can still overwrite an update when the application reuses old values.</description></item>
<item><title>Correlated SSD failures: what the Alibaba measurements count</title><link>https://hesela.com/analyses/ssd-correlated-failures-nodes-racks/</link><guid isPermaLink="false">https://hesela.com/analyses/ssd-correlated-failures-nodes-racks/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Han et al. (FAST 2021) report that 12.9% of failures were intra-node and 18.3% intra-rack at a 30-minute grouping threshold. These are shares of recorded failures, not percentages of all installed drives. Reading the analysis code also separates a group-size statistic from a prediction of the next drive failure.</description></item>
<item><title>SSD mapping caches: why DRAM size is not a speed rating</title><link>https://hesela.com/analyses/ssd-mapping-cache-hmb/</link><guid isPermaLink="false">https://hesela.com/analyses/ssd-mapping-cache-hmb/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>Separate SSD maps from data buffers, explain cache admission and HMB, and reproduce memory, scan and request-versus-byte hit examples.</description></item>
<item><title>SSD firmware-hour failures: model, revision and runtime matter</title><link>https://hesela.com/analyses/ssd-power-on-hours-firmware-failures/</link><guid isPermaLink="false">https://hesela.com/analyses/ssd-power-on-hours-firmware-failures/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>A healthy wear indicator does not rule out a firmware-hour defect. Vendor advisories describe separate 32,768-, 40,000- and 28,224-hour issues with different affected models and recovery outcomes. Match the exact drive and firmware, then check fresh runtime evidence.</description></item>
<item><title>SSD thermal throttling: temperature and NVMe counters</title><link>https://hesela.com/analyses/ssd-thermal-throttling-failures/</link><guid isPermaLink="false">https://hesela.com/analyses/ssd-thermal-throttling-failures/#updated-2026-10-16</guid><pubDate>Fri, 16 Oct 2026 00:00:00 GMT</pubDate><description>A hot SSD reading, a thermal-management event and a drive failure are different observations. Historical fleet studies show platform-dependent temperature associations, not a universal failure threshold. NVMe exposes distinct temperature and action counters; their units, capabilities and specification revision determine what a reading can establish.</description></item></channel></rss>
