NAND Read Disturb: Shoo Fly, Don’t Bother Me
Back at Denali MemCon, I thought I heard Numonyx’ CTO Ed Doller discuss an unfamiliar read-failure mechanism in NAND Flash memories. Yet when I investigated it, my closest sources told me I’d imagined it. Reading NAND Flash wasn’t destructive, they told me. Well, I had a chance to interview Doller at last week’s Flash Memory Summit and he confirmed that I’d heard something memorable. He’d listed it as a read-endurance problem for NAND Flash.
The problem is called read-disturb and it’s apparently not discussed much by NAND Flash vendors, but all of their parts have this problem and you need to know about it. Why? Because every time you read from a NAND Flash page, you’re partially writing to the cells in most of the page. Do this enough times and the bit cells in the page start to forget. That would be bad. It doesn’t cause the device to wear out but it does cause problems.
So how does this read disturb work? Take a look at this drawing:

The drawing shows sixteen bit cells in a NAND Flash device. Each bit cell consists of nothing more than a MOSFET with a floating gate. To find out if there are any electrons trapped on a particular floating gate, the memory device must read out an entire word. It does this by putting a zero on the gates of all the bit cells in a word via the word line. However, because of the organization of the NAND Flash pages, the memory must also put some voltage on the gates of all the other MOSFETs in the block to turn on all of the other FETs in series in each bit line. NAND Flash memories are organized into strings of FETs to make them compact, small, cheap.
The high voltage on the MOSFETs’ gates attracts electrons to the floating gates, which is sort of like a write pulse, only shorter. Eventually, over time, some of those electrons will make it to the bit cell’s floating gate. When enough electrons make the jump, the cumulative read cycles will have caused a write and the data will be wrong. That’s the read-disturb problem. All NAND Flash parts have this problem and so the problem needs to be managed accordingly by periodically scrubbing each page in the NAND Flash memory. Doller recalls popping NAND Flash parts on the IC tester and reading them to death.
Now before you go all alarmist, realize that core memory and DRAMs also have read-disturb issues. Reading either type of memory drains the bit from the bit cell and the state must be restored before the next read from that location. It’s not a problem only because core-memory subsystems were and DRAM chips are designed to handle the problem. Managing NAND Flash is no different.
Stiggle commented:
Steve Leibson commented:
Stiggle commented:
Steve Leibson commented:
Steve Leibson commented:
Stiggle commented:















