That's up to you. But if you have one of the SSD models the article is about, Linux probably won't help. It might make it worse.
Linux is beautifully optimised for performance. Linux is more likely to write the same data more quickly than Windows, when an application has a large amount of data to write. So if the problem is the SSD fails when a large amount of data is written quickly but within specs, then it's likely to fail on Linux too.
Unless it's a bug in the Windows driver. But it sounds from descriptions that it isn't a bug in Windows, it's a bug in the SSD that went unnoticed because not many people wrote large amounts of data quickly on systems with those SSDs.
So it sounds like there may be a model-specific blacklist required in the driver, to detect particular SSDs and reduce the speed they are written to, because they fail when run at the speed they advertise to the OS.
Or, alternatively, it sounds like those models may require a firmware upgrade from the SSD vendor.
If either of those are required, a similar workaround will be required in the Linux driver too, to avoid the same problem as soon as someone runs a similar application on Linux.
Unfortunately, even with a speed-limiting blacklist in the driver, whether in Window or Linux, those SSD models probably still corrupt data from time to time, because speed alone is unlikely to be the underlying cause of corruption. A vendor firmware update, or vendor confirmation that a specific change in the driver avoids the SSD bug, are what's required.
You are saying we are going to see similar reports for Linux when using these parts? Why did it started happening after a windows update then? And why did it need a patch?
>You are saying we are going to see similar reports for Linux when using these parts?
The linux install base is orders of magnitude smaller than windows, so there's less of a chance that it gets picked up by tech media. Moreover if it's really an issue with the underlying hardware itself, a more technical user base would be able to trace the issue to the actual hardware, rather than going straight to social media with "ZOMG windows update bricked my PC!"
>Why did it started happening after a windows update then?
Some sort of code change that changes the behavior of the drive, but is technically within spec.
>And why did it need a patch?
Because putting in a patch doesn't imply you're at fault. The linux kernel is filled with workarounds for crappy hardware as well. The existence of those workarounds don't imply linux was somehow at fault for those bugs.
> if it's really an issue with the underlying hardware itself, a more technical user base would be able to trace the issue to the actual hardware, rather than going straight to social media with "ZOMG windows update bricked my PC!"
So what you are saying is that users went "ZOMG windows update bricked my PC!" And that prompted the article?
> Because putting in a patch doesn't imply you're at fault
If you designed a system for certain range of hardware, your latest update broke that design and you had to go back and put a patch, I'd say it's pretty much Microsoft at fault here, even though your comment is right
>So what you are saying is that users went "ZOMG windows update bricked my PC!" And that prompted the article?
Most tech "journalism" is basically regurgitating stuff from reddit/twitter/other tech sites, so yes.
>If you designed a system for certain range of hardware, your latest update broke that design and you had to go back and put a patch, I'd say it's pretty much Microsoft at fault here, even though your comment is right
So there's no accounting for which party broke the spec? Whoever touched it last is at fault?
Although that bug report is for ZFS on the same SSD as the Windows article (WD SN770), the faults described in the Linux bug report look like would also happen with ext4 or btrfs.
So I searched for reported problems with SN770 and ext4, and found enough results to convince me.
That particular SSD fails with Linux and ext4 too.
Linux is beautifully optimised for performance. Linux is more likely to write the same data more quickly than Windows, when an application has a large amount of data to write. So if the problem is the SSD fails when a large amount of data is written quickly but within specs, then it's likely to fail on Linux too.
Unless it's a bug in the Windows driver. But it sounds from descriptions that it isn't a bug in Windows, it's a bug in the SSD that went unnoticed because not many people wrote large amounts of data quickly on systems with those SSDs.
So it sounds like there may be a model-specific blacklist required in the driver, to detect particular SSDs and reduce the speed they are written to, because they fail when run at the speed they advertise to the OS.
Or, alternatively, it sounds like those models may require a firmware upgrade from the SSD vendor.
If either of those are required, a similar workaround will be required in the Linux driver too, to avoid the same problem as soon as someone runs a similar application on Linux.
Unfortunately, even with a speed-limiting blacklist in the driver, whether in Window or Linux, those SSD models probably still corrupt data from time to time, because speed alone is unlikely to be the underlying cause of corruption. A vendor firmware update, or vendor confirmation that a specific change in the driver avoids the SSD bug, are what's required.