Re: Maybe we want to maintain a bad driver list? (Was 'Re: "bad tree block start, want 419774464 have 0" after a clean shutdown, could it be a disk firmware issue?')
From: David Sterba <hidden>
Date: 2021-07-22 13:57:40
On Thu, Jul 22, 2021 at 08:18:21AM +0800, Qu Wenruo wrote:
On 2021/7/22 上午1:44, David Sterba wrote:quoted
On Fri, Jul 16, 2021 at 11:44:21PM +0100, Jorge Bastos wrote:quoted
Hi, This was a single disk filesystem, DUP metadata, and this week it stop mounting out of the blue, the data is not a concern since I have a full fs snapshot in another server, just curious why this happened, I remember reading that some WD disks have firmware with write caches issues, and I believe this disk is affected: Model family:Western Digital Green Device model:WDC WD20EZRX-00D8PB0 Firmware version:80.00A80For the record summing up the discussion from IRC with Zygo, this particular firmware 80.00A80 on WD Green is known to have problematic firmware and would explain the observed errors. Recommendation is not to use WD Green or periodically disable the write cache by 'hdparm -W0'.Zygo is always the god to expose bad hardware. Can we maintain a list of known bad hardware inside btrfs-wiki? And maybe escalate it to other fses too?
Yeah a list on wiki would be great, though I'm a bit skeptical about keeping it up up to date, there are very few active wiki editors, the knowledge is still mostly stored in the IRC logs. But without a landing page on wiki we can't even start, so I'll create it.