Skip to main content
NetApp Knowledge Base

RHEL Host showing different lun size compared to the actual size of the lun on the storage end

Views:
207
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
SAN
Last Updated:

Applies to

  • Ontap 9
  • RHEL Clustered Host

Issue

  • RHEL Host is showing a different size (9TB in this example) compared to what is the actual lun size(5TB in this example) for all newly created luns.
  • When a test lun is provisioned to the clustered RHEL hosts, some nodes could see the lun and some could not.
  • sg_inq and sg_readcap -v outputs on RHEL Host shows that the host can read the target lun and was even showing the correct size , however it was not reflecting the correct size on host end.

output-sg_inq and sg_readcap -v .png

  • df-h shows it as mounted on host end.
  • Stale entries observed on host end in var/log/messages, which can cause unnecessary load on multipath and can lead the host to behave in abnormal way.

RHEL Host showing different lun size

  • Host was reading the size from these stale entries for some of the luns as the previous lun attached was of some other size and the current lun attached is of a different size.

RHEL Host showing different lun size compared to the actual size of the lun on the storage end

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.