為什麼 omreport storage vdisk controller=0 跨伺服器的輸出不一致

為什麼 omreport storage vdisk controller=0 跨伺服器的輸出不一致

我編寫了一個腳本來取得最新 VirtualDisk 的 RAID 配置。

在一台伺服器上我得到:

# omreport storage vdisk controller=0 -fmt ssv | awk '-F;' '/^ID/{print}/Virtual\s*Disk\s*[0-9]+;/{line=$0;value=$7}END{print line;print value}'
ID;Status;Name;State;Hot Spare Policy violated;Encrypted;Layout;Size;T10 Protection Information Status;Associated Fluid Cache State ;Device Name;Bus Protocol;Media;Read Policy;Write Policy;Cache Policy;Stripe Element Size;Disk Cache Policy
14;Ok;VirtualDisk16;Ready;Not Applicable;No;RAID-0;7,451.50 GB (8000987201536 bytes);No;Not Applicable;/dev/sdo;SAS;HDD;No Read Ahead;Write Through;Not Applicable;64 KB;Unchanged
RAID-0
#

在另一台伺服器上,我得到:

# omreport storage vdisk controller=0 -fmt ssv | awk '-F;' '/^ID/{print}/Virtual\s*Disk\s*[0-9]+;/{line=$0;value=$7}END{print line;print value}'
ID;Status;Name;State;Hot Spare Policy violated;Virtual Disk Bad Blocks;Encrypted;Layout;Size;T10 Protection Information Status;Associated Fluid Cache State ;Device Name;Bus Protocol;Media;Read Policy;Write Policy;Cache Policy;Stripe Element Size;Disk Cache Policy
16;Ok;Virtual Disk 16;Ready;Not Applicable;No;No;RAID-0;3,725.50 GB (4000225165312 bytes);No;Not Applicable;/dev/sdp;SAS;HDD;Read Ahead;Force Write Back;Not Applicable;64 KB;Disabled
No
#

這兩台伺服器之間的差異在於 PERC H730 Mini 韌體版本:

據此omreport system version,第一個有PERC H730 Mini v25.5.2.0001第二個PERC H730 Mini v25.5.0.0018

答案1

這可能取決於不同的omreport韌體版本。一般來說,要小心地針對非常特定的輸出自訂腳本,因為任何小的更改都可能會破壞您的解析。

相關內容