Changes between Initial Version and Version 1 of Ticket #1313


Ignore:
Timestamp:
Apr 2, 2020, 4:57:37 PM (4 years ago)
Author:
Christian Franke
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1313 – Description

    initial v1  
    1010What's worse, they're shipping DM-SMR drives as "RAID" and "NAS" drives
    1111
    12 This is causing MAJOR problems - such as the latest iteration of WD REDs (WDx0EFAX replacing WDx0EFRX) being unable to be used for rebuilding RAID[56] or ZFS RAIDZ sets: They rebuiild for a while (1-2 hours), then throw errors and get kicked out of the set.
     12This is causing MAJOR problems - such as the latest iteration of WD REDs (WDx0EFAX replacing WDx0EFRX) being unable to be used for rebuilding RAID![56] or ZFS RAIDZ sets: They rebuiild for a while (1-2 hours), then throw errors and get kicked out of the set.
    1313
    1414
    1515When this happens, the drives themselves report such oddities in the logs as "IDNF" ("Sector ID not found") when interrogated with smartctl -x
    16 
     16{{{
    1717----
    1818Error 451 [18] occurred at disk power-on lifetime: 286 hours (11 days + 22 hours)
    … …  
    3333  61 00 a0 00 00 00 00 cf ae b9 b8 40 00  8d+03:27:28.765  WRITE FPDMA QUEUED
    3434----
     35}}}
    3536
    3637This manifests in Linux kernel as:
    37 
     38{{{
    3839[20809.396248] blk_update_request: critical target error, dev sdd, sector 3484334368 op 0x1:(WRITE) flags 0x700 phys_seg 2 prio class 0
    3940[20809.396275] sd 0:0:3:0: [sdd] tag#830 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK
    … …  
    4445[20809.396289] blk_update_request: I/O error, dev sdd, sector 3484334520 op 0x1:(WRITE) flags 0x700 phys_seg 2 prio class 0
    4546----
     47}}}
    4648
    4749I'd originally thought this was due to them reading ahead to areas not yet recorded in the shingled area in use and getting an unformatted block(*), but 100% zero-filling a drive resulted in the same errors.
    … …  
    5759
    5860for a WD40EFAX
    59 
     61{{{
    6062hdparm -I shows:
    6163           *    Data Set Management TRIM supported (limit 10 blocks)
    6264           *    Deterministic read ZEROs after TRIM
    63 
     65}}}
    6466
    6567And to make matters worse, not all DM-SMR drives are doing this - for example Seagate ST3000DM-007 are DM-SMR but don't report TRIM capabilities
    … …  
    7375
    7476"Two dimensional magnetic recording"(TDMR) is a necessary part of SMR (shingled+zoning), but the marketers don't see it that way. The effect is the same and the implications of both are the same.
    75 
    76 
    77