I got it resolved finally, I had to push NetApp support a lot, but they managed to point me to the right direction in the end.
So, there were two separate issues that I mistakenly combined:
1. Missing paths were due to wrong zoning. It sounds silly, but I couldn't spot it.
2. "kernel: scsi: host 0 channel 3 id 0 lun4194304 has a LUN larger than allowed by the host adapter" error message comes from HP RAID controller, it has nothing to do with NetApp filers.
Key here is to pay attention to details: "host 0 channel 3 id 0" tells exactly what target it is about, also 'lsscsi' utility comes handy in here.
Here is a quote from RedHat's KB article about the error message:
Smart Array Physical Devices Example
# lsscsi [4:0:0:0] disk HP LOGICAL VOLUME 6.00 /dev/sdb /dev/sg0 [4:3:0:0] storage HP P220i 6.00 - /dev/sg1
And within /var/log/messages file:
: Apr 9 10:54:17 hostname kernel: scsi: host 4 channel 3 id 0 lun4194304 has a LUN larger than allowed by the host adapter :
Within the above example, the Smart Array raid controller device at scsi address 4:3:0:0 returns a lun list which includes a lun id value of 4194304. This id value is in a vendor specific format. This is one of the physical devices behind the controller that would typically be used as part of the logical volume. Since only the logical volumes should be accessed by the system, this physical lun number can be ignored. Typically only HP health agents would access information on the physical disk devices via the raid controller device. Not all combinations of Smart Array model, firmware, and hpsa driver revisions will report physical disk devices back to the host. Normally these devices are filtered off in later hpsa driver / Smart Array firmware combinations.
Cheers, Vladimir
On Mon, Oct 12, 2015 at 3:17 PM, Momonth momonth@gmail.com wrote:
So RedHat has a KB article for it https://access.redhat.com/solutions/67157 and it's advised to contact storage appliance vendor.