Re: IPv6 on hypersockets
On Wed, 2012-05-09 at 13:57 -0400, Bauer, Bobby (NIH/CIT) [E] wrote: ping doesn't work yet but one step at a time. Bobby, use ping6 for IPv6; ping works just for IPv4. Kind regards, Ursula Braun, IBM Germany -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES 11 SP1 msg: kernel: scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter
On Wed, May 9, 2012 at 6:11 PM, Mike Walter mike.wal...@aonhewitt.com wrote: ... 11:12:11 scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter May 7 11:12:11 L98ZAT11 kernel: scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter Yeah ... what Ray said. It's a little confusing because the acronym expands to Logical Unit Number but we commonly use LUN to refer to the storage volume and not its number (presented by the fabric or storage array or SVC). My experience with SAN on SuSE is getting a bit dated, but I do not recall such a limit. Since this is the second SAN based storage volume on this guest, you can gain from the experience you already have: Did you get all four paths working with the first vol? Oracle changes things. If it were for anything else, I would say to throw all SAN vols into LVM as PVs, then dole out LVs as needed. If it were my shop, I'd still do that when serving Oracle, but I will not speculate about their optimizations w/r/t driving storage directly. Did you manage the first SAN vol via LVM? In any case, are your multipath tools up to date? Like Ray also said, get current with the patches. On SLE 11, it is as easy as 'zypper up'. -- R; Rick Troth Velocity Software http://www.velocitysoftware.com/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: SLES 11 SP1 msg: kernel: scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter
On Wednesday, 05/09/2012 at 09:39 EDT, Raymond
Higgs/Poughkeepsie/IBM@IBMUS wrote:
11:12:11 scsi: host 0 channel 0 id 0 lun2 has a LUN larger than
allowed by the host adapter
There shouldn't be any limitations until 2 TB. I don't think linux is
complaining about the size of the lun. I think linux is complaining
about
the lun number. It is saying that it will only configure luns 0x
and
0x0001.
Nominally, that response means that the LUN number of one of the LUNs
returned on REPORT LUNS is larger than the value supported by the adapter,
which zfcp_scsi_adapter_register() sets to 0x. Those are
(supposed to be) unsigned ints, so the implication is, as you suggested,
that something changed this value via sysfs, assuming it is exported.
From drivers/scsi/scsi_scan.c:
1466 if (lun sdev-host-max_lun) {
1467printk(KERN_WARNING scsi: %s lun%d has a LUN
larger
1468than allowed by the host adapter\n,
1469 devname, lun);
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: SLES 11 SP1 msg: kernel: scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter
Linux on 390 Port LINUX-390@vm.marist.edu wrote on 05/10/2012 10:02:58
AM:
From: Alan Altmark/Endicott/IBM@IBMUS
To: LINUX-390@vm.marist.edu
Date: 05/10/2012 10:14 AM
Subject: Re: SLES 11 SP1 msg: kernel: scsi: host 0 channel 0 id 0
lun2 has a LUN larger than allowed by the host adapter
Sent by: Linux on 390 Port LINUX-390@vm.marist.edu
On Wednesday, 05/09/2012 at 09:39 EDT, Raymond
Higgs/Poughkeepsie/IBM@IBMUS wrote:
11:12:11 scsi: host 0 channel 0 id 0 lun2 has a LUN larger than
allowed by the host adapter
There shouldn't be any limitations until 2 TB. I don't think linux is
complaining about the size of the lun. I think linux is complaining
about
the lun number. It is saying that it will only configure luns 0x
and
0x0001.
Nominally, that response means that the LUN number of one of the LUNs
returned on REPORT LUNS is larger than the value supported by the
adapter,
which zfcp_scsi_adapter_register() sets to 0x. Those are
(supposed to be) unsigned ints, so the implication is, as you suggested,
that something changed this value via sysfs, assuming it is exported.
From drivers/scsi/scsi_scan.c:
1466 if (lun sdev-host-max_lun) {
1467printk(KERN_WARNING scsi: %s lun%d has a
LUN
larger
1468than allowed by the host
adapter\n,
1469 devname, lun);
I think you're looking at the wrong kernel. Max_lun gets set to 1 by
zfcp. If the storage array returned more luns than the report_luns
command had room for, than there would be a message about increasing the
value of some kernel parm, like
/sys/module/scsi_mod/parameters/max_report_luns.
We have never tested HP storage here. I know some of it is rebranded
Hitachi, which we do test. I'm leaning towards linux not recognizing the
vendor and model info from the scsi inquiry command. My best guess.
Regards,
Ray Higgs
System z FCP Firmware Development
Bld. 706, B42
2455 South Road
Poughkeepsie, NY 12601
(845) 435-8666, T/L 295-8666
rayhi...@us.ibm.com
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
Re: SLES 11 SP1 msg: kernel: scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter
Thanks Rick, Ray, Pedro, and Alan, It’s not fixed yet, but the pointer to scsi-logging-level (for the rescan-scsi-bus.sh, I entered: scsi-logging-level –all 7 –s”) has provided significant new information: scsi 0:0:0:0: scsi scan: peripheral qualifier of 3, device not added scsi 0:0:0:0: scsi scan: consider passing scsi_mod.dev_flags=HP:DISK-SUBSYSTEM:0x240 or 0x1000240 In full, it yielded: 14:04:40 rescan-scsi-bus.sh 14:04:40 Host adapter 0 (zfcp) found. Scanning SCSI subsystem for new devices Scanning host 0 scsi 0:0:0:0: scsi scan: INQUIRY pass 1 length 36 scsi 0:0:0:0: Send: 0xfb99b200 scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 24 00 buffer = 0xfc6c0300, bufflen = 36, queuecommand 0x03c002e8e8dc leaving scsi_dispatch_cmnd() scsi 0:0:0:0: Done: 0xfb99b200 SUCCESS scsi 0:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 24 00 scsi 0:0:0:0: scsi host busy 1 failed 0 scsi 0:0:0:0: Notifying upper driver of completion (result 0) 0 sectors total, 36 bytes done. scsi scan: INQUIRY successful with code 0x0 scsi 0:0:0:0: scsi scan: INQUIRY pass 2 length 212 scsi 0:0:0:0: Send: 0xfb99b200 scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 d4 00 buffer = 0xfc6c0300, bufflen = 212, queuecommand 0x03c002e8e8dc leaving scsi_dispatch_cmnd() scsi 0:0:0:0: Done: 0xfb99b200 SUCCESS scsi 0:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK scsi 0:0:0:0: CDB: 14:04:40 Inquiry: 12 00 00 00 d4 00 scsi 0:0:0:0: scsi host busy 1 failed 0 scsi 0:0:0:0: Notifying upper driver of completion (result 0) 0 sectors total, 212 bytes done. scsi scan: INQUIRY successful with code 0x0 scsi 0:0:0:0: scsi scan: peripheral qualifier of 3, device not added scsi 0:0:0:0: scsi scan: consider passing scsi_mod.dev_flags=HP:DISK-SUBSYSTEM:0x240 or 0x1000240 scsi scan: Sending REPORT LUNS to host 0 channel 0 id 0 (try 0) scsi 0:0:0:0: Send: 0xfb99b200 scsi 0:0:0:0: CDB: Report luns: a0 00 00 00 00 00 00 00 10 00 00 00 buffer = 0xfc6c0300, bufflen = 4096, queuecommand 0x03c002e8e8dc leaving scsi_dispatch_cmnd() scsi 0:0:0:0: Done: 0xfb99b200 SUCCESS scsi 0:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK scsi 0:0:0:0: CDB: Report luns: a0 00 00 00 00 00 00 00 10 00 00 00 scsi 0:0:0:0: scsi host busy 1 failed 0 scsi 0:0:0:0: Notifying upper driver of completion (result 0) 8 sectors total, 4096 bytes done. scsi scan: REPORT LUNS successful (try 0) result 0x0 scsi 0:0:0:0: scsi scan: REPORT LUN scan 14:05:23 scsi scan: device exists on 0:0:0:1 scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter for all SCSI target IDs, all LUNs Scanning for device 0 0 0 0 ... scsi 0:0:0:0: scsi scan: INQUIRY pass 1 length 36 scsi 0:0:0:0: Send: 0xf3b66f00 scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 24 00 buffer = 0xed579f00, bufflen = 36, queuecommand 0x03c002e8e8dc leaving scsi_dispatch_cmnd() scsi 0:0:0:0: Done: 0xf3b66f00 SUCCESS scsi 0:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 24 00 scsi 0:0:0:0: scsi host busy 1 failed 0 scsi 0:0:0:0: Notifying upper driver of completion (result 0) 0 sectors total, 36 bytes done. scsi scan: INQUIRY successful with code 0x0 scsi 0:0:0:0: scsi scan: INQUIRY pass 2 length 212 scsi 0:0:0:0: Send: 0xf3b66f00 scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 d4 00 buffer = 0xed579f00, bufflen = 212, queuecommand 0x03c002e8e8dc leaving scsi_dispatch_cmnd() scsi 0:0:0:0: Done: 0xf3b66f00 SUCCESS scsi 0:0:0:0: Result: hostbyte=DID_OK driverbyte=DRIVER_OK scsi 0:0:0:0: CDB: Inquiry: 12 00 00 00 d4 00 scsi 0:0:0:0: scsi host busy 1 failed 0 scsi 0:0:0:0: Notifying upper driver of completion (result 0) 0 sectors total, 212 bytes done. scsi scan: INQUIRY successful with code 0x0 scsi 0:0:0:0: scsi scan: peripheral qualifier of 3, device not added scsi 0:0:0:0: scsi scan: consider passing scsi_mod.dev_flags=HP:DISK-SUBSYSTEM:0x240 or 0x1000240 0 new device(s) found. 0 device(s) removed. 14:05:29 L98ZAT11:~ # May 10 14:04:40 L98ZAT11 kernel: leaving scsi_dispatch_cmnd() May 10 14:04:40 L98ZAT11 kernel: 0 sectors total, 36 bytes done. May 10 14:04:40 L98ZAT11 kernel: leaving scsi_dispatch_cmnd() May 10 14:04:40 L98ZAT11 kernel: 0 sectors total, 212 bytes done. May 10 14:04:40 L98ZAT11 kernel: leaving scsi_dispatch_cmnd() May 10 14:04:40 L98ZAT11 kernel: 8 sectors total, 4096 bytes done. May 10 14:04:40 L98ZAT11 kernel: scsi: host 0 channel 0 id 0 lun2 has a LUN larger than allowed by the host adapter May 10 14:04:40 L98ZAT11 kernel: leaving scsi_dispatch_cmnd() May 10 14:04:40 L98ZAT11 kernel: 0 sectors total, 36 bytes done. May 10 14:04:40 L98ZAT11 kernel: leaving scsi_dispatch_cmnd() May 10 14:04:40 L98ZAT11 kernel: 0 sectors total, 212 bytes done. I will “consider passing scsi_mod.dev_flags=HP:DISK-SUBSYSTEM:0x240 or 0x1000240.”, as soon as figure out
