Michel Salim wrote:
Though it would be nice to have a tool that would provide enough information to make a warranty claim -- does btrfs keep enough information for such a tool to be written?
Failed device I/O (rather than bad checksums and other fs-specific error detections) should be logged at a lower layer in the standard system logs. Warranties are really about who you buy your drives from, if you go cheap don't expect any replacements. If you buy quality stuff, the failures usually occur right after the warranty expires :) In the case of bad manufacturing batches, the good vendors figure that out real fast and don't hassle you about replacing them as they fail. And even from a good vendor, don't expect you can run a drive with a 1-year 20% duty-cycle warranty like it was a 100% duty-cycle drive and get the vendor to replace them if they fail in < 1 year. People often complain the vendor does not stand behind the warranty when they are really badly violating the usage terms. jim -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
