1 |
antlists wrote: |
2 |
> On 16/06/2020 12:26, Dale wrote: |
3 |
>> I've also read about the resilvering problems too. I think LVM |
4 |
>> snapshots and something about BTFS(sp?) has problems. I've also read |
5 |
>> that on windoze, it can cause a system to freeze while it is trying |
6 |
>> to rewrite the moved data too. It gets so slow, it actually makes |
7 |
>> the OS not respond. I suspect it could happen on Linux to if the |
8 |
>> conditions are right. |
9 |
>> |
10 |
> Being all technical, what seems to be happening is ... |
11 |
> |
12 |
> Random writes fillup the PMR cache. The drive starts flushing the |
13 |
> cache, but unfortunately you need a doubly linked list or something - |
14 |
> you need to be able to find the physical block from the logical |
15 |
> address (for reading) and to find the logical block from the physical |
16 |
> address (for cache-flushing). So once the cache fills, the drive needs |
17 |
> "down time" to move stuff around, and it stops responding to the bus. |
18 |
> There are reports of disk stalls of 10 minutes or more - bear in mind |
19 |
> desktop drives are classed as unsuitable for raid because they stall |
20 |
> for *up* *to* *two* minutes ... |
21 |
> |
22 |
>> I guess this is about saving money for the drive makers. The part |
23 |
>> that seems to really get under peoples skin tho, them putting those |
24 |
>> drives out there without telling people that they made changes that |
25 |
>> affect performance. It's bad enough for people who use them where |
26 |
>> they work well but the people that use RAID and such, it seems to |
27 |
>> bring them to their knees at times. I can't count the number of |
28 |
>> times I've read that people support a class action lawsuit over |
29 |
>> shipping SMR without telling anyone. It could happen and I'm not |
30 |
>> sure it shouldn't. People using RAID and such, especially in some |
31 |
>> systems, they need performance not drives that beat themselves to death. |
32 |
> |
33 |
> Most manufacturers haven't been open, but at least - apart from WD - |
34 |
> they haven't been stupid either. Bear in mind WD actively market their |
35 |
> Red drives as suitable for NAS or Raid, putting SMR in there was |
36 |
> absolutely dumb. Certainly in the UK, as soon as news starts getting |
37 |
> round, they'll probably find themselves (or rather their retailers |
38 |
> will get shafted with) loads of returns as "unfit for purpose". And, |
39 |
> basically, they have a legal liability with no leg to stand on because |
40 |
> if a product doesn't do what it's advertised for, then the customer is |
41 |
> *entitled* to a refund. |
42 |
> |
43 |
> Dunno why, I've never been a WD fan, so I dodged that bullet. I just |
44 |
> caught another one, because I regularly advise people they shouldn't |
45 |
> be running Barracudas, while running two myself ... :-) |
46 |
> |
47 |
> Cheers, |
48 |
> Wol |
49 |
> |
50 |
> |
51 |
|
52 |
|
53 |
From what I've read, all the drive makers were selling SMR without |
54 |
telling anyone at first. It wasn't just WD but Seagate as well. There |
55 |
was another maker as well but can't recall what the brand was. I want |
56 |
to say HGST but could have been something else. I tend to like WD and |
57 |
Seagate and have had a couple Toshibas as well. I've had a WD go bad |
58 |
but I've had a Seagate go bad too. I'm of the mindset that most drives |
59 |
are good but on occasion, you hit a bad batch. No matter what brand it |
60 |
is, there is a horror story out there somewhere. I've been lucky so |
61 |
far. It seems SMART catches that a drive is failing before it actually |
62 |
does. I had one that gave the 24 hour warning and it wasn't kidding |
63 |
either. Another just starting reporting bad spots. I replaced it |
64 |
before it corrupted anything. I've never lost data that I can recall tho. |
65 |
|
66 |
I've read that if there is a lawsuit, the EU will likely be first and |
67 |
the easiest. If you say something should work in a certain way and it |
68 |
doesn't, refund for sure. Given the large scale of this, lawsuit is |
69 |
possible. I'm no lawyer but I do think what the makers did in hiding |
70 |
this info is wrong. It doesn't matter what brand it is, they should be |
71 |
honest about their products. This is especially true for situations |
72 |
like RAID, NAS and other 24/7 systems. Thing is, even my system falls |
73 |
into that category. I run 24/7 here except during power failures. LVM |
74 |
likely requires a better drive than a regular home type system that is |
75 |
only used a little each day. Commercial type systems that are in heavy |
76 |
use, they require a really heavy duty components. Claiming something is |
77 |
or leaving out info that shows they are not is not good. They should |
78 |
have known it would bite them at some point. People have far to many |
79 |
tools to test drives and uncover the truth. |
80 |
|
81 |
Little update. The drive passed its first SMART long test. I started |
82 |
badblocks hours ago and it is almost done. It's at 96% right now. I |
83 |
think it lists bad blocks as it finds them and so far, it hasn't listed |
84 |
any. I'll post the results when it is done. So far, the drive I bought |
85 |
seems to be in very good condition. |
86 |
|
87 |
Now to wait on the last little bit to finish. Just hope it doesn't get |
88 |
right to the end and start blowing smoke. :/ |
89 |
|
90 |
Dale |
91 |
|
92 |
:-) :-) |