PowerFlex 裝置有修正的讀取錯誤

Summary: SDS 裝置出現錯誤,指出「裝置有固定的讀取錯誤」。

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

案例

當 SDS 裝置讀取 SDS 更正的錯誤時,可能會發生這種情況。

當禁用或啟用後台掃描程式時,可能會發生這種情況。

症狀

裝置上的固定錯誤可以顯示在以下位置:

  • GUI 顯示錯誤:

  • 「--query_sds --sds_id <SDS_ID>」輸出顯示每個裝置的計數器,並修正讀取錯誤:

15: Name: /dev/sdr Path: /dev/sdr Original-path: /dev/sdr ID: 2d63f7c80003000e
           Storage Pool: SAS_pool1, Capacity: 1116 GB Error-fixes: 6 scanned 0 MB, Compare errors: 0 State: Normal

MDM getInfoDump 中的counters_dump.txt會顯示不同物件上的FIXED_READ_ERROR_COUNT:

ID: df7700a600120012 DEVICE_TYPE                READ_ERR                                    FIXED_READ_ERROR_COUNT   1
ID: 1d1e4e5500000012 SDS_TYPE                   READ_ERR                                    FIXED_READ_ERROR_COUNT   1
ID: 1c34e1f700000007 STORAGE_POOL_TYPE          READ_ERR                                    FIXED_READ_ERROR_COUNT   1
ID: b9b286df00000001 PROTECTION_DOMAIN_TYPE     READ_ERR                                    FIXED_READ_ERROR_COUNT   1
ID: 49b6b8057d1fc84b SYSTEM_TYPE                READ_ERR                                    FIXED_READ_ERROR_COUNT   1
注意:MDM 事件記錄中沒有事件可指出已看到此「修正讀取錯誤」情況。

其他可能的癥狀:裝置可能處於「錯誤」狀態。系統訊息或系統記錄中的區塊裝置上可能出現錯誤:

blk_update_request: critical medium error, dev sdr, sector 94390272
  sd 0:2:15:0: [sdr] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
  sd 0:2:15:0: [sdr] tag#1 Sense Key : Medium Error [current] 
  sd 0:2:15:0: [sdr] tag#1 Add. Sense: Unrecovered read error

SDS trc 中可能會有很長的傳輸 I/O 訊息:

contDevMngr_HandleLongInflightIoViolation:02998: IO on devId: 2d63f7c80003000e (/dev/sdr) took too long, Low threshold exceeded - waited for reaper 12250 millis
contDevMngr_HandleLongInflightIoViolation:02998: IO on devId: 2d63f7c80003000e (/dev/sdr) took too long, Low threshold exceeded - waited for reaper 13250 millis
contDevMngr_HandleLongInflightIoViolation:02998: IO on devId: 2d63f7c80003000e (/dev/sdr) took too long, Low threshold exceeded - waited for reaper 14250 millis

SDS sdbg_out.txt中的裝置 I/O 計數器可能有錯誤:

13: Dev path:/dev/sdr Size(lbs):0 Time grn:520577464
  Io Counters:
   GENERAL
     Writes: 4852 Lbs: 2160443 MBs: 1054 Errors: 0
     Reads: 49283 Lbs: 111376 MBs: 54 Errors: 12744
   BM
     Writes: 0 Lbs: 0 MBs: 0 Errors: 0
     Reads: 0 Lbs: 0 MBs: 0 Errors: 0
   COMB_MAP
     Writes: 5 Lbs: 1390 MBs: 0 Errors: 2
     Reads: 0 Lbs: 0 MBs: 0 Errors: 0
   TOOTH_MAP
     Writes: 426 Lbs: 688528 MBs: 336 Errors: 424
     Reads: 0 Lbs: 0 MBs: 0 Errors: 0
   IO
     Writes: 4319 Lbs: 603064 MBs: 294 Errors: 16
     Reads: 2076 Lbs: 16608 MBs: 8 Errors: 22

根據counters_dump.txt,裝置的延遲可能很高:

ID: 2d63f7c60003000c DEVICE_TYPE                DEV_LATENCY                          AVG_WRITE_LATENCY_IN_MICROSEC   0
ID: 2d63f7c70003000d DEVICE_TYPE                DEV_LATENCY                          AVG_WRITE_LATENCY_IN_MICROSEC   0
ID: 2d63f7c80003000e DEVICE_TYPE                DEV_LATENCY                          AVG_WRITE_LATENCY_IN_MICROSEC   11424
ID: 2d63f7c90003000f DEVICE_TYPE                DEV_LATENCY                          AVG_WRITE_LATENCY_IN_MICROSEC   0
ID: 2d63f7ca00030010 DEVICE_TYPE                DEV_LATENCY                          AVG_WRITE_LATENCY_IN_MICROSEC   0

 

影響

「Fixed Read Errors」計數器對系統不會有任何直接影響

但是,它可能表示可能導致 SDS 中斷連線、重建活動等的潛在狀況。

Cause

當 SDS 裝置具有已使用鏡像副本更正或修復的讀取錯誤時,可以看到這種情況。在以下情況下,可能會進行更正:      

  • 後台掃描程式無法讀取數據的一個副本,並使用另一個副本覆蓋它。
  • SDS 由於無法讀取磁碟而無法處理 SDC 的讀取要求,而是使用次要複本來處理 I/O 並覆寫本機資料。

此警告表示磁碟可能正在變慢、發生壞機或具有損壞磁區。上述機制重寫塊,可以修復“軟”壞塊。

Resolution

  • 檢查磁碟。如有必要,請與硬體供應商聯繫以進行更換。
    計數器通常會指出基礎狀況,且磁碟即將損壞。上述 SDS 動作是嘗試修正軟不良磁區,但並非在所有情況下都能成功。
     
  • 清除計數器。

scli --reset_scanner_error_counters --protection_domain_id <pd id> --storage_pool_id <sp id> --reset_corrected_read_error_counter
Article Properties
Article Number: 000174344
Article Type: Solution
Last Modified: 19 Sept 2025
Version:  6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.