On Fri, 26 Feb 2010 16:08:53 -0500 Chris Mason <chris.ma...@oracle.com> wrote: > > The problem is that with a writeback cache, any write is likely > to be missed on power failures. journalling in general requires some > notion of being able to wait for block A to be on disk before you write > block B, and that's difficult to do when the disk lies about what is > really there ;) >
Hi, Has anyone managed to make a list of drive models which are suspect of lying about what has really hit the disk surface, or of not hounouring barriers? Can anyone share any cases where your investigation turned positive evidence that a drive model was defective in this respect? This is so worrying that I think we should understand why are manufacturers doing this: is it firmware bugs? Is it to inflate benchmarks? Are they shoving crap on the cheaper drives' firmware to force "enterprise" people to buy the more expensive SAS models? If one could publish a list of known defective drives, maybe we could put some shame on the manufacturers or even convince them to fix their firmware. Failing that, we might at least be able to avoid the known bad models. Any insight into this subject will be appreciated. Best regards Cláudio -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
