Skip to main content
NetApp Knowledge Base

Applications crash and won't run on ONTAP 9.7 LUNs

Views:
263
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
san
Last Updated:

Applies to

 

  • ONTAP 9.7 and later
  • Linux
  • Oracle ASM with ASMFD
  • MongoDB
  • GPFS

Issue

 

  • Some applications do not respect the host SCSI layer default max_sectors_kb and require a custom setting through a custom udev rule or multipath.conf configuration to set greater than the default of 64KB.
  • If the host respects the max_sector_kb setting of 1024 (1MB) for transfer sizes and an amount larger than 1024 is configured it will revert to 64KB transfers.  If the application requires larger transfers than 64KB it will fail to operate properly.
  • With ONTAP 9.7 All SAN Array an illegal request will be returned to the host and the application will not function if transfers being made are larger than 1MB.
  • With ONTAP 9.7 non-All SAN array transfers larger than 1MB will be allowed and a debug message will be logged scsiblade.invalid.xfer.len as for non-All SAN arrays the limit is not enforced until a later version of ONTAP for non-All SAN arrays

Sat Sep 10 12:35:26 +0300 [NTAP-CLUS1-01: scsit_lu_1: scsiblade.invalid.xfer.len:notice]: Host type VMWARE sent command opcode 0x2a with a transfer length of 1212420 bytes, which exceeds the maximum of 1MB on LUN 80BdL+N-YTYV.


 

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support