开始新对话

此帖子已超过 5 年

Solved!

Go to Solution

2580

2013年11月15日 03:00

如何确定分的盘是主机的

EMC工程师给主机划过盘,业务厂商发现一台主机上有3块未label的盘,但不确定是否是给这台主机使用的,操作系统是solaris 10,阵列式DMX4

盘分给主机后,被VXVM卷管理软件管理,能否确定3块未label的盘就是10.123.50.55上的盘?这三块盘是否被其他主机还使用,存储上有命令能查到吗?

10.123.50.55  使用vxdisk list 输出:

DEVICE       TYPE            DISK         GROUP        STATUS

disk_0       auto:none       -            -            online invalid

disk_1       auto:none       -            -            online invalid

disk_2       auto:cdsdisk    -            -            online

disk_3       auto:cdsdisk    -            -            online

disk_4       auto:cdsdisk    nios_dg04    nios_dg      online

disk_5       auto:cdsdisk    nios_dg05    nios_dg      online

disk_6       auto:cdsdisk    -            -            online

disk_7       auto:cdsdisk    -            -            online

disk_8       auto:cdsdisk    -            -            online

disk_9       auto:cdsdisk    -            -            online

disk_10      auto:cdsdisk    nios_dg06    nios_dg      online

disk_11      auto:cdsdisk    -            -            online

emc_clariion1_5 auto:cdsdisk    bakdg01      bakdg        online

emc_clariion1_16 auto:cdsdisk    bakdg02      bakdg        online

emc_clariion1_26 auto:cdsdisk    bakdg03      bakdg        online

emc0_03b0    auto:cdsdisk    nios_dg01    nios_dg      online

emc0_03c8    auto:cdsdisk    nios_dg02    nios_dg      online

emc0_03e0    auto:cdsdisk    nios_dg03    nios_dg      online

emc0_03f8    auto            -            -            error

emc0_15af    auto            -            -            nolabel

emc0_15a2    auto            -            -            nolabel

emc0_16a3    auto:cdsdisk    nios_dg07    nios_dg      online failing

emc0_16bc    auto:cdsdisk    nios_dg08    nios_dg      online failing

emc0_16d5    auto:cdsdisk    nios_dg09    nios_dg      online failing

emc0_16ee    auto:cdsdisk    nios_dg10    nios_dg      online

emc0_168a    auto:cdsdisk    nios_dg11    nios_dg      online

emc0_176b    auto:cdsdisk    nios_dg12    nios_dg      online

emc0_0320    auto            -            -            error

emc0_0338    auto            -            -            error

emc0_0350    auto            -            -            error

emc0_0368    auto            -            -            error

emc0_0380    auto            -            -            error

emc0_0398    auto            -            -            error

emc0_1595    auto            -            -            nolabel

emc0_1658    auto:cdsdisk    nios_dg13    nios_dg      online

emc0_1671    auto:cdsdisk    nios_dg14    nios_dg      online

emc0_1707    auto:cdsdisk    nios_dg15    nios_dg      online

emc0_1720    auto:cdsdisk    nios_dg16    nios_dg      online

emc0_1739    auto:cdsdisk    nios_dg17    nios_dg      online

emc0_1752    auto:cdsdisk    nios_dg18    nios_dg      online

2.1K 消息

2013年11月17日 16:00

你这台10.123.50.55,如果装了Solutions Enabler的话,直接运行sympd  list,就可以看到对应你这台机器上所被扫到带有主机物理链路的盘了,你可以试试看。

258 消息

2013年11月15日 03:00

#luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
  Node WWN:5006048452aa6608  Device Type:Disk device
    Logical Path:/dev/rdsk/c3t5006048452AA6608d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c4t5006048452AA6607d0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047C720000087B94BFC94BCd0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047C720000087BB4BFC951Dd0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047C720000088854C11742Bd0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047C720000088884C11757Ed0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047CDE60000AF1A4BFC951Ad0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047CDE60000AF1D4BFC9581d0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047CDE60000AF2F4BFCA488d0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047CDE60000AF324BFCA505d0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047CDE60000AFE54C1174F5d0s2
  Node WWN:200800a0b847cde6  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600A0B800047CDE60000B0EE4C19CE96d0s2
  Node WWN:50060160c1e0e39f  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060160241022006152E23EEA96DF11d0s2
  Node WWN:50060160c1e0e39f  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t600601602410220028450872EA96DF11d0s2
  Node WWN:50060160c1e0e39f  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060160241022005651FF6BEA96DF11d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030333830d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030333638d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030333530d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030333338d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030333230d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031354146d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031354132d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031353935d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030334230d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030334338d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030334530d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031363538d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031363731d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031363841d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031364133d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031364243d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031364435d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031364545d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031373037d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031373230d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031373339d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031373532d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533031373642d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030334638d0s2
  Node WWN:5006048452aa6607  Device Type:Disk device
    Logical Path:/dev/rdsk/c6t60060480000290105752533030333938d0s2
  Node WWN:500104f000af26ea  Device Type:Tape device
    Logical Path:/dev/rmt/1n
  Node WWN:500104f000af26e7  Device Type:Tape device
    Logical Path:/dev/rmt/2n
  Node WWN:500104f000af26f0  Device Type:Tape device
    Logical Path:/dev/rmt/3n
  Node WWN:500104f000af26ed  Device Type:Tape device
    Logical Path:/dev/rmt/4n
  Node WWN:500104f000af26f3  Device Type:Tape device
    Logical Path:/dev/rmt/5n
  Node WWN:500104f000af26f6  Device Type:Tape device
    Logical Path:/dev/rmt/6n
  Node WWN:500104f000af26f9  Device Type:Tape device
    Logical Path:/dev/rmt/7n
  Node WWN:500104f000af26fc  Device Type:Tape device
    Logical Path:/dev/rmt/8n
root@COUNDB # format
Searching for disks...done

c3t5006048452AA6608d0: configured with capacity of 0.94MB
c4t5006048452AA6607d0: configured with capacity of 0.94MB
c6t60060480000290105752533031354146d0: configured with capacity of 483.66GB
c6t60060480000290105752533031353935d0: configured with capacity of 483.66GB
c6t60060480000290105752533031354132d0: configured with capacity of 483.66GB


AVAILABLE DISK SELECTIONS:
       0. c0t0d0
          /ssm@0,0/pci@1c,700000/pci@1/scsi@2/sd@0,0
       1. c0t1d0
          /ssm@0,0/pci@1c,700000/pci@1/scsi@2/sd@1,0
       2. c3t5006048452AA6608d0
          /ssm@0,0/pci@18,600000/SUNW,qlc@2/fp@0,0/ssd@w5006048452aa6608,0
       3. c4t5006048452AA6607d0
          /ssm@0,0/pci@18,600000/SUNW,qlc@2,1/fp@0,0/ssd@w5006048452aa6607,0
       4. c6t600A0B800047C720000087B94BFC94BCd0
          /scsi_vhci/ssd@g600a0b800047c720000087b94bfc94bc
       5. c6t600A0B800047C720000087BB4BFC951Dd0
          /scsi_vhci/ssd@g600a0b800047c720000087bb4bfc951d
       6. c6t600A0B800047C720000088854C11742Bd0
          /scsi_vhci/ssd@g600a0b800047c720000088854c11742b
       7. c6t600A0B800047C720000088884C11757Ed0
          /scsi_vhci/ssd@g600a0b800047c720000088884c11757e
       8. c6t600A0B800047CDE60000AF1A4BFC951Ad0
          /scsi_vhci/ssd@g600a0b800047cde60000af1a4bfc951a
       9. c6t600A0B800047CDE60000AF1D4BFC9581d0
          /scsi_vhci/ssd@g600a0b800047cde60000af1d4bfc9581
      10. c6t600A0B800047CDE60000AF2F4BFCA488d0
          /scsi_vhci/ssd@g600a0b800047cde60000af2f4bfca488
      11. c6t600A0B800047CDE60000AF324BFCA505d0
          /scsi_vhci/ssd@g600a0b800047cde60000af324bfca505
      12. c6t600A0B800047CDE60000AFE54C1174F5d0
          /scsi_vhci/ssd@g600a0b800047cde60000afe54c1174f5
      13. c6t600A0B800047CDE60000B0EE4C19CE96d0
          /scsi_vhci/ssd@g600a0b800047cde60000b0ee4c19ce96
      14. c6t60060160241022006152E23EEA96DF11d0
          /scsi_vhci/ssd@g60060160241022006152e23eea96df11
      15. c6t600601602410220028450872EA96DF11d0
          /scsi_vhci/ssd@g600601602410220028450872ea96df11
      16. c6t60060160241022005651FF6BEA96DF11d0
          /scsi_vhci/ssd@g60060160241022005651ff6bea96df11
      17. c6t60060480000290105752533031364243d0
          /scsi_vhci/ssd@g60060480000290105752533031364243
      18. c6t60060480000290105752533031364133d0
          /scsi_vhci/ssd@g60060480000290105752533031364133
      19. c6t60060480000290105752533031363841d0
          /scsi_vhci/ssd@g60060480000290105752533031363841
      20. c6t60060480000290105752533031363731d0
          /scsi_vhci/ssd@g60060480000290105752533031363731
      21. c6t60060480000290105752533031363538d0
          /scsi_vhci/ssd@g60060480000290105752533031363538
      22. c6t60060480000290105752533031354146d0
          /scsi_vhci/ssd@g60060480000290105752533031354146
      23. c6t60060480000290105752533031353935d0
          /scsi_vhci/ssd@g60060480000290105752533031353935
      24. c6t60060480000290105752533030334530d0
          /scsi_vhci/ssd@g60060480000290105752533030334530
      25. c6t60060480000290105752533030334338d0
          /scsi_vhci/ssd@g60060480000290105752533030334338
      26. c6t60060480000290105752533030334230d0
          /scsi_vhci/ssd@g60060480000290105752533030334230
      27. c6t60060480000290105752533030334638d0
          /scsi_vhci/ssd@g60060480000290105752533030334638
      28. c6t60060480000290105752533030333938d0
          /scsi_vhci/ssd@g60060480000290105752533030333938
      29. c6t60060480000290105752533030333830d0
          /scsi_vhci/ssd@g60060480000290105752533030333830
      30. c6t60060480000290105752533030333638d0
          /scsi_vhci/ssd@g60060480000290105752533030333638
      31. c6t60060480000290105752533030333530d0
          /scsi_vhci/ssd@g60060480000290105752533030333530
      32. c6t60060480000290105752533030333338d0
          /scsi_vhci/ssd@g60060480000290105752533030333338
      33. c6t60060480000290105752533030333230d0
          /scsi_vhci/ssd@g60060480000290105752533030333230
      34. c6t60060480000290105752533031373642d0
          /scsi_vhci/ssd@g60060480000290105752533031373642
      35. c6t60060480000290105752533031373532d0
          /scsi_vhci/ssd@g60060480000290105752533031373532
      36. c6t60060480000290105752533031373339d0
          /scsi_vhci/ssd@g60060480000290105752533031373339
      37. c6t60060480000290105752533031373230d0
          /scsi_vhci/ssd@g60060480000290105752533031373230
      38. c6t60060480000290105752533031373037d0
          /scsi_vhci/ssd@g60060480000290105752533031373037
      39. c6t60060480000290105752533031364545d0
          /scsi_vhci/ssd@g60060480000290105752533031364545
      40. c6t60060480000290105752533031364435d0
          /scsi_vhci/ssd@g60060480000290105752533031364435
      41. c6t60060480000290105752533031354132d0
          /scsi_vhci/ssd@g60060480000290105752533031354132

1.2K 消息

2013年11月17日 17:00

楼主,这里列出的emc0_15af是vxvm的节点设备,我们可以通过vxdmpdbprint得到它的native device,也就是cxtxdx,之后通过inq命令知道它是什么厂商的。

找不到事件!

Top