"Momonth" == Momonth momonth@gmail.com writes:
Do you have the ostype set correctly? Same initiators on the CentOS 6.7 working system as on the busted on? I assum you did something like:
lun create -vserver foo /vol/bar/lun1 -size 1g -ostype linux
and it's messed up? Did you try creating a new small test lun on the busted setup and seeing if that lun has too big a lun ID?
What does the 'lun show -m' on the problematic lun show? Since it's working on one HBA, but not the other... that semi implies to me that you have an HBA config issue.
Trying to create a new test lun might help figure out what's going on here?
Momonth> Funky enough .. I have the 2nd cluster in the other DC, running 8.3.1, Momonth> with CentOS 6.7 initiator (with default version of HBA drivers, Momonth> firmwares) that doesn't experience this issue ... I conclude it has Momonth> something to do with SVM configuration.
Momonth> On Mon, Oct 12, 2015 at 3:17 PM, Momonth momonth@gmail.com wrote:
Hi,
Before I take a long journey with NetApp support, let me ask you guys.
I have CentOS 6.7 server and I'm trying to attach a cDOT LUN to it as path discovery fails with:
kernel: scsi: host 0 channel 3 id 0 lun4194304 has a LUN larger than allowed by the host adapter
However it only fails with the message above for one HBA out of two installed into the server. The HBAs (drivers, firmware etc) are identical. The HBA are Qlogic relabeled as HP.
So RedHat has a KB article for it https://access.redhat.com/solutions/67157 and it's advised to contact storage appliance vendor.
I've seen that once, it was due to some FW files being absent under /lib/firmware, it's not the same this time.
Has anyone seen that before?
Cheers, Vladimir
Momonth> _______________________________________________ Momonth> Toasters mailing list Momonth> Toasters@teaparty.net Momonth> http://www.teaparty.net/mailman/listinfo/toasters