Theodore Tso wrote:There is extensive per sector error correction on each sector written. What you would see in this case (or many, many other possible ways drives can corrupt media) is a "media error" on the next read. You would never get back the partially written contents of that sector at the host. Having our tools (fsck especially) be resilient in the face of media errors is really critical. Although I don't think the scenario of a partially written sector is common, media errors in general are common and can develop over time. See the NetApp paper from Sigmetrics 2007 for some interesting analysis... ric --
| Mark Lord | Re: Linux 2.6.24-rc7 |
| Kentaro Takeda | [TOMOYO 05/15](repost) Domain transition handler functions. |
| Willy Tarreau | Re: Linux v2.6.24-rc1 |
| Al Boldi | [RFD] Incremental fsck |
| drew | Re: SVGA-alphanum. modes |
| Kevin Cummings | VESA video support during boot. |
| Raymond Nijssen | Re: What the 17" monitor reviews never tell you |
| Michael Haardt | GNU shell utils 1.7: date(1) dumps core (with easy solution:) |
git: | |
| David Woodhouse | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jarek Poplawski | Re: [BUG] New Kernel Bugs |
