Solved: non zero used-column for partner-disks in sysconfig -r

cheese123 · ‎2016-01-05

Hi

i have several nodes with the following output in sysconfig -r:

...

RAID Disk       Device          HA SHELF BAY CHAN Pool Type RPM Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
partner         sw2_rz2:6.102   4c    6   6   FC:B   0 FCAL 15000 0/0               420156/860480768
partner         sw1_rz2:7.21    4a    1   5   FC:A   0 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:7.19    4b    1   3   FC:A   1 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:6.82    4a    5   2   FC:A   1 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:7.28    4a    1   12 FC:A   1 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:6.101   4b    6   5   FC:A   1 FCAL 15000 0/0               420156/860480768
partner         sw2_rz2:6.97    4d    6   1   FC:B   0 FCAL 15000 0/0               420156/860480768
partner         sw1_rz2:6.103   4a    6   7   FC:A   0 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:6.102   4a    6   6   FC:A   1 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:8.20    4a    1   4   FC:A   1 FCAL 15000 418000/856064000 420156/860480768
partner         sw2_rz2:6.107   4d    6   11 FC:B   0 FCAL 15000 0/0               420156/860480768
partner         sw1_rz1:6.87    4b    5   7   FC:A   1 FCAL 15000 0/0               420156/860480768

i would expect only zeros in the used-column of partner disks

this is a metro-cluster ontap 8.1.4P8 7-Mode

Is there something i should be worried about?

yours

josef

Renifa · ‎2016-01-11

Hi,

There is nothing to worry about this output. That is because filer does not access data on partner disks unless it does the takeover. In order to know the used size of the disk, RAID must read table of contents from that disk. Therefore, RAID usually reports only raw size of partner disks that results in showing used size for some, but not all partner disks.

Refer KB 3012254 "https://kb.netapp.com/support/index?page=content&id=3012254&actp=search&viewlocale=en_US&searchid=1452500241097" for more information and the Bug details.

Hope this helps.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

View solution in original post

Renifa · ‎2016-01-11

Hi,

There is nothing to worry about this output. That is because filer does not access data on partner disks unless it does the takeover. In order to know the used size of the disk, RAID must read table of contents from that disk. Therefore, RAID usually reports only raw size of partner disks that results in showing used size for some, but not all partner disks.

Refer KB 3012254 "https://kb.netapp.com/support/index?page=content&id=3012254&actp=search&viewlocale=en_US&searchid=1452500241097" for more information and the Bug details.

Hope this helps.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

georgevj · ‎2016-01-27

Seems like the link is broken. use the following link or search for KB id 3012254

https://kb.netapp.com/support/index?page=content&id=3012254

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.
Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.

nicholsongc · ‎2016-12-27

Not to belabor the point but WHY some and not others?

The partner clearly was able to determine the USED info for one disk (sw1_rz1:8.20). What is the reasoning behind "some but not others"?