This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Linux nodes not picking up expanded SAN capacity

One of our SAN volumes got expanded (w/o changing its signature). Linux nodes (CentOS, RHEL) are sticking with the old pre-expansion capacity in Orion despite showing the right (expanded) capacity via 'df'. Deleting the volume via "list resources" or via "manage nodes", and then re-adding it doesn't do a thing.

Screen Shot 2015-05-19 at 12.57.50 AM.png

$ df

...

/dev/cvfsctl2_DataDrive 655811737600 98421208960 557390528640  16% /Volumes/DataDrive

OSX and Windows nodes picked up the expanded capacity just fine.

Screen Shot 2015-05-19 at 12.58.53 AM.png

What could be the cause of it?

  • It appears Net-SNMP implementation on Linux incorrectly reports large capacity volumes.

    Linux snmpwalks of two SAN volumes, 90 and 600TB respectively:

    HOST-RESOURCES-MIB::hrStorageAllocationUnits.39 = INTEGER: 65536 Bytes
    HOST-RESOURCES-MIB::hrStorageAllocationUnits.40 = INTEGER: 65536 Bytes
    HOST-RESOURCES-MIB::hrStorageSize.39 = INTEGER: 1465091712
    HOST-RESOURCES-MIB::hrStorageSize.40 = INTEGER: 1657123808

    OSX snmpwalks of the same (except in reverse order: 600TB and 90TB, respectively):

    HOST-RESOURCES-MIB::hrStorageAllocationUnits.39 = INTEGER: 524288 Bytes
    HOST-RESOURCES-MIB::hrStorageAllocationUnits.41 = INTEGER: 65536 Bytes
    HOST-RESOURCES-MIB::hrStorageSize.39 = INTEGER: 1280882300
    HOST-RESOURCES-MIB::hrStorageSize.41 = INTEGER: 1465091712

    Note the allocation size.

    snmp version on OSX: 5.6. Linux: net-snmp-libs-5.5-49.el6n (one of them).

    Latest Net-SNMP builds (5.7.1 and later) appear to have fixed it for RHEL - so I just need to figure out how to update these packages?