* Pb with external RAID controller in lk 2.4
@ 2002-05-21 17:28 Fabien Salvi
2002-05-22 0:03 ` Gérard Roudier
2002-05-22 7:49 ` Fabien Salvi
0 siblings, 2 replies; 9+ messages in thread
From: Fabien Salvi @ 2002-05-21 17:28 UTC (permalink / raw)
To: linux-scsi; +Cc: Lorraine Suschetet
Hello, I have problem when using the lk 2.4
My system :
- A bi-pentium II 450 processor with 1 GB RAM
- Symbios/LSILogic SCSI card NCR 53c895
- external Mylex DAC960SX RAID Controller (Ultra2 scsi) in a Siemens
enclosure
1) With kernel 2.2 (exactly 2.2.19, but it's the same through 2.2.9 to
2.2.19), I have no problems, my disks are visible without problems :
May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 8,
function 0
May 17 16:22:28 node01 kernel: sym53c8xx: 53c876 detected with Symbios
NVRAM
May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 8,
function 1
May 17 16:22:28 node01 kernel: sym53c8xx: 53c876 detected with Symbios
NVRAM
May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 1,
function 0
May 17 16:22:28 node01 kernel: sym53c8xx: 53c895 detected with Symbios
NVRAM
May 17 16:22:28 node01 kernel: sym53c876-0: rev 0x14 on pci bus 2 device
8 function 0 irq 15
May 17 16:22:28 node01 kernel: sym53c876-0: Symbios format NVRAM, ID 7,
Fast-20, Parity Checking
May 17 16:22:28 node01 kernel: sym53c876-0: on-chip RAM at 0xf4202000
May 17 16:22:28 node01 kernel: sym53c876-0: restart (scsi reset).
May 17 16:22:28 node01 kernel: sym53c876-0: Downloading SCSI SCRIPTS.
May 17 16:22:28 node01 kernel: sym53c876-1: rev 0x14 on pci bus 2 device
8 function 1 irq 5
May 17 16:22:28 node01 kernel: sym53c876-1: Symbios format NVRAM, ID 7,
Fast-20, Parity Checking
May 17 16:22:28 node01 kernel: sym53c876-1: on-chip RAM at 0xf4203000
May 17 16:22:28 node01 kernel: sym53c876-1: restart (scsi reset).
May 17 16:22:28 node01 kernel: sym53c876-1: Downloading SCSI SCRIPTS.
May 17 16:22:28 node01 kernel: sym53c895-2: rev 0x1 on pci bus 2 device
1 function 0 irq 10
May 17 16:22:28 node01 kernel: sym53c895-2: Symbios format NVRAM, ID 7,
Fast-40, Parity Checking
May 17 16:22:28 node01 kernel: sym53c895-2: on-chip RAM at 0xf4201000
May 17 16:22:28 node01 kernel: sym53c895-2: restart (scsi reset).
May 17 16:22:28 node01 kernel: sym53c895-2: Downloading SCSI SCRIPTS.
May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 8,
function 0
May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2400[0..127] is in
use
May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 8,
function 1
May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2800[0..127] is in
use
May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 1,
function 0
May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2000[0..127] is in
use
May 17 16:22:28 node01 kernel: scsi0 : sym53c8xx-1.7.1-20000726
May 17 16:22:28 node01 kernel: scsi1 : sym53c8xx-1.7.1-20000726
May 17 16:22:28 node01 kernel: scsi2 : sym53c8xx-1.7.1-20000726
May 17 16:22:28 node01 kernel: scsi : 3 hosts.
May 17 16:22:28 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:22:28 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:22:28 node01 kernel: Detected scsi disk sda at scsi0, channel
0, id 0, lun 0
May 17 16:22:28 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:22:28 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:22:28 node01 kernel: Detected scsi disk sdb at scsi0, channel
0, id 0, lun 1
May 17 16:22:28 node01 kernel: sym53c876-0-<0,0>: tagged command queue
depth set to 8
May 17 16:22:28 node01 kernel: sym53c876-0-<0,1>: tagged command queue
depth set to 8
May 17 16:22:28 node01 kernel: Vendor: NEC Model: CD-ROM
DRIVE:466 Rev: 1.17
May 17 16:22:28 node01 kernel: Type:
CD-ROM ANSI SCSI revision: 02
May 17 16:22:28 node01 kernel: Detected scsi CD-ROM sr0 at scsi2,
channel 0, id 5, lun 0
May 17 16:22:28 node01 kernel: Vendor: SIEMENS Model: STM/L
S1 Rev: 4.1b
May 17 16:22:28 node01 kernel: Type:
Processor ANSI SCSI revision: 02
May 17 16:22:28 node01 kernel: Detected scsi generic sg3 at scsi2,
channel 0, id 8, lun 0
May 17 16:22:28 node01 kernel: scsi : detected 4 SCSI generics 1 SCSI
cdrom 2 SCSI disks total.
May 17 16:22:28 node01 kernel: sym53c895-2-<5,*>: FAST-20 SCSI 20.0 MB/s
(50 ns, offset 16)
May 17 16:22:28 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
xa/form2 cdda tray
May 17 16:22:28 node01 kernel: Uniform CD-ROM driver Revision: 3.11
May 17 16:22:28 node01 kernel: sym53c876-0-<0,*>: FAST-20 SCSI 20.0 MB/s
(50 ns, offset 16)
May 17 16:22:28 node01 kernel: SCSI device sda: hdwr sector= 512 bytes.
Sectors= 17776640 [8680 MB] [8.7 GB]
May 17 16:22:28 node01 kernel: SCSI device sdb: hdwr sector= 512 bytes.
Sectors= 17776640 [8680 MB] [8.7 GB]
It founds the real 2 disks exporting from the RAID controller (in fact
2*2 disks in RAID 1)
2) with 2.4.18 kernel, I've got this :
May 17 16:19:36 node01 kernel: sym0: <875> rev 0x14 on pci bus 2 device
8 function 0 irq 15
May 17 16:19:36 node01 kernel: sym0: Symbios NVRAM, ID 7, Fast-20, HVD,
parity checking
May 17 16:19:36 node01 kernel: sym0: open drain IRQ line driver, using
on-chip SRAM
May 17 16:19:36 node01 kernel: sym0: using LOAD/STORE-based firmware.
May 17 16:19:36 node01 kernel: sym0: SCSI BUS has been reset.
May 17 16:19:36 node01 kernel: sym1: <875> rev 0x14 on pci bus 2 device
8 function 1 irq 5
May 17 16:19:36 node01 kernel: sym1: Symbios NVRAM, ID 7, Fast-20, HVD,
parity checking
May 17 16:19:36 node01 kernel: sym1: open drain IRQ line driver, using
on-chip SRAM
May 17 16:19:36 node01 kernel: sym1: using LOAD/STORE-based firmware.
May 17 16:19:36 node01 kernel: sym1: SCSI BUS has been reset.
May 17 16:19:36 node01 kernel: sym2: <895> rev 0x1 on pci bus 2 device 1
function 0 irq 10
May 17 16:19:36 node01 kernel: sym2: Symbios NVRAM, ID 7, Fast-40, LVD,
parity checking
May 17 16:19:36 node01 kernel: sym2: open drain IRQ line driver, using
on-chip SRAM
May 17 16:19:36 node01 kernel: sym2: using LOAD/STORE-based firmware.
May 17 16:19:36 node01 kernel: sym2: SCSI BUS has been reset.
May 17 16:19:36 node01 kernel: scsi0 : sym-2.1.17a
May 17 16:19:36 node01 kernel: scsi1 : sym-2.1.17a
May 17 16:19:36 node01 kernel: scsi2 : sym-2.1.17a
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
8680T1 Rev: 1339
May 17 16:19:36 node01 kernel: Type:
Direct-Access ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: sym0:0:0: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:1: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:2: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:3: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:4: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:5: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:6: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: sym0:0:7: tagged command queuing enabled,
command queue depth 16.
May 17 16:19:36 node01 kernel: Vendor: NEC Model: CD-ROM
DRIVE:466 Rev: 1.17
May 17 16:19:36 node01 kernel: Type:
CD-ROM ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Vendor: SIEMENS Model: STM/L
S1 Rev: 4.1b
May 17 16:19:36 node01 kernel: Type:
Processor ANSI SCSI revision: 02
May 17 16:19:36 node01 kernel: Attached scsi disk sda at scsi0, channel
0, id 0, lun 0
May 17 16:19:36 node01 kernel: Attached scsi disk sdb at scsi0, channel
0, id 0, lun 1
May 17 16:19:36 node01 kernel: Attached scsi disk sdc at scsi0, channel
0, id 0, lun 2
May 17 16:19:36 node01 kernel: Attached scsi disk sdd at scsi0, channel
0, id 0, lun 3
May 17 16:19:36 node01 kernel: Attached scsi disk sde at scsi0, channel
0, id 0, lun 4
May 17 16:19:36 node01 kernel: Attached scsi disk sdf at scsi0, channel
0, id 0, lun 5
May 17 16:19:36 node01 kernel: Attached scsi disk sdg at scsi0, channel
0, id 0, lun 6
May 17 16:19:36 node01 kernel: Attached scsi disk sdh at scsi0, channel
0, id 0, lun 7
May 17 16:19:36 node01 kernel: Attached scsi CD-ROM sr0 at scsi2,
channel 0, id 5, lun 0
May 17 16:19:36 node01 kernel: sym2:5: FAST-20 SCSI 20.0 MB/s ST (50.0
ns, offset 16)
May 17 16:19:36 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
xa/form2 cdda tray
May 17 16:19:36 node01 kernel: Uniform CD-ROM driver Revision: 3.12
May 17 16:19:36 node01 kernel: sym0:0: FAST-20 SCSI 20.0 MB/s ST (50.0
ns, offset 16)
May 17 16:19:36 node01 kernel: SCSI device sda: 17776640 512-byte hdwr
sectors (9102 MB)
May 17 16:19:36 node01 kernel: Partition check:
May 17 16:19:36 node01 kernel: sda: sda1 sda2 sda3 sda4
May 17 16:19:36 node01 kernel: SCSI device sdb: 17776640 512-byte hdwr
sectors (9102 MB)
May 17 16:19:36 node01 kernel: sdb: sdb1
Like you can see, it founds 8 disks !
I tried to increase max_scsi_luns to 64 to see if it will find as many
disks as luns, but it does not go after lun7 ==> 8 disks
There are 3 drivers in linux kernel 2.4.18 that supports may SCSI HBA
(sym53c8xx,sym53c8xx_2 and ncr53c8xx) but I have always the same
results...
Infortunately, I can't make tests with other cards, because I don't have
them !
(scsi hvd connectors).
Well, I don't know why the lk founds as many disks...
What do you think about it ?
Do you have any idea ?
Thanks in advance for your help !
-------------
Fabien SALVI Centre de Ressources Informatiques
Archamps, France -- http://www.cri74.org
PingOO GNU/linux distribution : http://www.pingoo.org
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Pb with external RAID controller in lk 2.4
2002-05-21 17:28 Pb with external RAID controller in lk 2.4 Fabien Salvi
@ 2002-05-22 0:03 ` Gérard Roudier
2002-05-22 1:03 ` Douglas Gilbert
2002-05-22 7:49 ` Fabien Salvi
1 sibling, 1 reply; 9+ messages in thread
From: Gérard Roudier @ 2002-05-22 0:03 UTC (permalink / raw)
To: Fabien Salvi; +Cc: linux-scsi, Lorraine Suschetet
A lun limitation is hardcoded in /usr/src/linux/drivers/scsi/scsi.c.
here's the offending lines:
#ifdef CONFIG_SCSI_MULTI_LUN
static int max_scsi_luns = 8;
#else
static int max_scsi_luns = 1;
#endif
You want to change value 8 by some higher value. It has chance to work.
The sym-1 driver is for long hardcoded to 16 LUNs. This should be the case
of the driver version you are using.
If you need more LUNS (up to 64), you can change the value in the
appropriate driver header: SCSI_NCR_MAX_LUN in sym53c8xx_defs.h
sym-2 is probably set up for eight LUNS. You want to edit sym_conf.h and
change SYM_SETUP_MAX_LUN to some higher value (up to 64):
/*
* Supported maximum number of LUNs to announce to
* the access method.
* The driver supports up to 64 LUNs per target as
* required by SPI-2/SPI-3. However some SCSI devices
* designed prior to these specifications or not being
* conformant may be highly confused when they are
* asked about a LUN > 7.
*/
#ifndef SYM_SETUP_MAX_LUN
#define SYM_SETUP_MAX_LUN (8)
#endif
Let me know if this fixes.
Regards,
Gérard.
On Tue, 21 May 2002, Fabien Salvi wrote:
> Hello, I have problem when using the lk 2.4
>
> My system :
> - A bi-pentium II 450 processor with 1 GB RAM
> - Symbios/LSILogic SCSI card NCR 53c895
> - external Mylex DAC960SX RAID Controller (Ultra2 scsi) in a Siemens
> enclosure
>
>
> 1) With kernel 2.2 (exactly 2.2.19, but it's the same through 2.2.9 to
> 2.2.19), I have no problems, my disks are visible without problems :
>
> May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 8,
> function 0
> May 17 16:22:28 node01 kernel: sym53c8xx: 53c876 detected with Symbios
> NVRAM
> May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 8,
> function 1
> May 17 16:22:28 node01 kernel: sym53c8xx: 53c876 detected with Symbios
> NVRAM
> May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 1,
> function 0
> May 17 16:22:28 node01 kernel: sym53c8xx: 53c895 detected with Symbios
> NVRAM
> May 17 16:22:28 node01 kernel: sym53c876-0: rev 0x14 on pci bus 2 device
> 8 function 0 irq 15
> May 17 16:22:28 node01 kernel: sym53c876-0: Symbios format NVRAM, ID 7,
> Fast-20, Parity Checking
> May 17 16:22:28 node01 kernel: sym53c876-0: on-chip RAM at 0xf4202000
> May 17 16:22:28 node01 kernel: sym53c876-0: restart (scsi reset).
> May 17 16:22:28 node01 kernel: sym53c876-0: Downloading SCSI SCRIPTS.
> May 17 16:22:28 node01 kernel: sym53c876-1: rev 0x14 on pci bus 2 device
> 8 function 1 irq 5
> May 17 16:22:28 node01 kernel: sym53c876-1: Symbios format NVRAM, ID 7,
> Fast-20, Parity Checking
> May 17 16:22:28 node01 kernel: sym53c876-1: on-chip RAM at 0xf4203000
> May 17 16:22:28 node01 kernel: sym53c876-1: restart (scsi reset).
> May 17 16:22:28 node01 kernel: sym53c876-1: Downloading SCSI SCRIPTS.
> May 17 16:22:28 node01 kernel: sym53c895-2: rev 0x1 on pci bus 2 device
> 1 function 0 irq 10
> May 17 16:22:28 node01 kernel: sym53c895-2: Symbios format NVRAM, ID 7,
> Fast-40, Parity Checking
> May 17 16:22:28 node01 kernel: sym53c895-2: on-chip RAM at 0xf4201000
> May 17 16:22:28 node01 kernel: sym53c895-2: restart (scsi reset).
> May 17 16:22:28 node01 kernel: sym53c895-2: Downloading SCSI SCRIPTS.
> May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 8,
> function 0
> May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2400[0..127] is in
> use
> May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 8,
> function 1
> May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2800[0..127] is in
> use
> May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 1,
> function 0
> May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2000[0..127] is in
> use
> May 17 16:22:28 node01 kernel: scsi0 : sym53c8xx-1.7.1-20000726
> May 17 16:22:28 node01 kernel: scsi1 : sym53c8xx-1.7.1-20000726
> May 17 16:22:28 node01 kernel: scsi2 : sym53c8xx-1.7.1-20000726
> May 17 16:22:28 node01 kernel: scsi : 3 hosts.
> May 17 16:22:28 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:22:28 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi disk sda at scsi0, channel
> 0, id 0, lun 0
> May 17 16:22:28 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:22:28 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi disk sdb at scsi0, channel
> 0, id 0, lun 1
> May 17 16:22:28 node01 kernel: sym53c876-0-<0,0>: tagged command queue
> depth set to 8
> May 17 16:22:28 node01 kernel: sym53c876-0-<0,1>: tagged command queue
> depth set to 8
> May 17 16:22:28 node01 kernel: Vendor: NEC Model: CD-ROM
> DRIVE:466 Rev: 1.17
> May 17 16:22:28 node01 kernel: Type:
> CD-ROM ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi CD-ROM sr0 at scsi2,
> channel 0, id 5, lun 0
> May 17 16:22:28 node01 kernel: Vendor: SIEMENS Model: STM/L
> S1 Rev: 4.1b
> May 17 16:22:28 node01 kernel: Type:
> Processor ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi generic sg3 at scsi2,
> channel 0, id 8, lun 0
> May 17 16:22:28 node01 kernel: scsi : detected 4 SCSI generics 1 SCSI
> cdrom 2 SCSI disks total.
> May 17 16:22:28 node01 kernel: sym53c895-2-<5,*>: FAST-20 SCSI 20.0 MB/s
> (50 ns, offset 16)
> May 17 16:22:28 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
> xa/form2 cdda tray
> May 17 16:22:28 node01 kernel: Uniform CD-ROM driver Revision: 3.11
> May 17 16:22:28 node01 kernel: sym53c876-0-<0,*>: FAST-20 SCSI 20.0 MB/s
> (50 ns, offset 16)
> May 17 16:22:28 node01 kernel: SCSI device sda: hdwr sector= 512 bytes.
> Sectors= 17776640 [8680 MB] [8.7 GB]
> May 17 16:22:28 node01 kernel: SCSI device sdb: hdwr sector= 512 bytes.
> Sectors= 17776640 [8680 MB] [8.7 GB]
>
> It founds the real 2 disks exporting from the RAID controller (in fact
> 2*2 disks in RAID 1)
>
>
> 2) with 2.4.18 kernel, I've got this :
> May 17 16:19:36 node01 kernel: sym0: <875> rev 0x14 on pci bus 2 device
> 8 function 0 irq 15
> May 17 16:19:36 node01 kernel: sym0: Symbios NVRAM, ID 7, Fast-20, HVD,
> parity checking
> May 17 16:19:36 node01 kernel: sym0: open drain IRQ line driver, using
> on-chip SRAM
> May 17 16:19:36 node01 kernel: sym0: using LOAD/STORE-based firmware.
> May 17 16:19:36 node01 kernel: sym0: SCSI BUS has been reset.
> May 17 16:19:36 node01 kernel: sym1: <875> rev 0x14 on pci bus 2 device
> 8 function 1 irq 5
> May 17 16:19:36 node01 kernel: sym1: Symbios NVRAM, ID 7, Fast-20, HVD,
> parity checking
> May 17 16:19:36 node01 kernel: sym1: open drain IRQ line driver, using
> on-chip SRAM
> May 17 16:19:36 node01 kernel: sym1: using LOAD/STORE-based firmware.
> May 17 16:19:36 node01 kernel: sym1: SCSI BUS has been reset.
> May 17 16:19:36 node01 kernel: sym2: <895> rev 0x1 on pci bus 2 device 1
> function 0 irq 10
> May 17 16:19:36 node01 kernel: sym2: Symbios NVRAM, ID 7, Fast-40, LVD,
> parity checking
> May 17 16:19:36 node01 kernel: sym2: open drain IRQ line driver, using
> on-chip SRAM
> May 17 16:19:36 node01 kernel: sym2: using LOAD/STORE-based firmware.
> May 17 16:19:36 node01 kernel: sym2: SCSI BUS has been reset.
> May 17 16:19:36 node01 kernel: scsi0 : sym-2.1.17a
> May 17 16:19:36 node01 kernel: scsi1 : sym-2.1.17a
> May 17 16:19:36 node01 kernel: scsi2 : sym-2.1.17a
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: sym0:0:0: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:1: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:2: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:3: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:4: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:5: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:6: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:7: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: Vendor: NEC Model: CD-ROM
> DRIVE:466 Rev: 1.17
> May 17 16:19:36 node01 kernel: Type:
> CD-ROM ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: SIEMENS Model: STM/L
> S1 Rev: 4.1b
> May 17 16:19:36 node01 kernel: Type:
> Processor ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Attached scsi disk sda at scsi0, channel
> 0, id 0, lun 0
> May 17 16:19:36 node01 kernel: Attached scsi disk sdb at scsi0, channel
> 0, id 0, lun 1
> May 17 16:19:36 node01 kernel: Attached scsi disk sdc at scsi0, channel
> 0, id 0, lun 2
> May 17 16:19:36 node01 kernel: Attached scsi disk sdd at scsi0, channel
> 0, id 0, lun 3
> May 17 16:19:36 node01 kernel: Attached scsi disk sde at scsi0, channel
> 0, id 0, lun 4
> May 17 16:19:36 node01 kernel: Attached scsi disk sdf at scsi0, channel
> 0, id 0, lun 5
> May 17 16:19:36 node01 kernel: Attached scsi disk sdg at scsi0, channel
> 0, id 0, lun 6
> May 17 16:19:36 node01 kernel: Attached scsi disk sdh at scsi0, channel
> 0, id 0, lun 7
> May 17 16:19:36 node01 kernel: Attached scsi CD-ROM sr0 at scsi2,
> channel 0, id 5, lun 0
> May 17 16:19:36 node01 kernel: sym2:5: FAST-20 SCSI 20.0 MB/s ST (50.0
> ns, offset 16)
> May 17 16:19:36 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
> xa/form2 cdda tray
> May 17 16:19:36 node01 kernel: Uniform CD-ROM driver Revision: 3.12
> May 17 16:19:36 node01 kernel: sym0:0: FAST-20 SCSI 20.0 MB/s ST (50.0
> ns, offset 16)
> May 17 16:19:36 node01 kernel: SCSI device sda: 17776640 512-byte hdwr
> sectors (9102 MB)
> May 17 16:19:36 node01 kernel: Partition check:
> May 17 16:19:36 node01 kernel: sda: sda1 sda2 sda3 sda4
> May 17 16:19:36 node01 kernel: SCSI device sdb: 17776640 512-byte hdwr
> sectors (9102 MB)
> May 17 16:19:36 node01 kernel: sdb: sdb1
>
> Like you can see, it founds 8 disks !
> I tried to increase max_scsi_luns to 64 to see if it will find as many
> disks as luns, but it does not go after lun7 ==> 8 disks
>
>
> There are 3 drivers in linux kernel 2.4.18 that supports may SCSI HBA
> (sym53c8xx,sym53c8xx_2 and ncr53c8xx) but I have always the same
> results...
>
> Infortunately, I can't make tests with other cards, because I don't have
> them !
> (scsi hvd connectors).
>
>
> Well, I don't know why the lk founds as many disks...
>
> What do you think about it ?
> Do you have any idea ?
>
> Thanks in advance for your help !
>
> -------------
> Fabien SALVI Centre de Ressources Informatiques
> Archamps, France -- http://www.cri74.org
> PingOO GNU/linux distribution : http://www.pingoo.org
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Pb with external RAID controller in lk 2.4
2002-05-22 0:03 ` Gérard Roudier
@ 2002-05-22 1:03 ` Douglas Gilbert
0 siblings, 0 replies; 9+ messages in thread
From: Douglas Gilbert @ 2002-05-22 1:03 UTC (permalink / raw)
To: Gérard Roudier; +Cc: Fabien Salvi, linux-scsi, Lorraine Suschetet
Gérard Roudier wrote:
>
> A lun limitation is hardcoded in /usr/src/linux/drivers/scsi/scsi.c.
> here's the offending lines:
>
> #ifdef CONFIG_SCSI_MULTI_LUN
> static int max_scsi_luns = 8;
> #else
> static int max_scsi_luns = 1;
> #endif
>
> You want to change value 8 by some higher value. It has chance to work.
You can set "max_scsi_luns" as a kernel boot time parameter
(e.g. with lilo add the line 'append "max_scsi_luns=16"') when
the scsi mid level is built in to the kernel. If the scsi mid
level is a module then the same argument can be given when that
module is loaded (or via /etc/modules.conf).
Doug Gilbert
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Pb with external RAID controller in lk 2.4
2002-05-21 17:28 Pb with external RAID controller in lk 2.4 Fabien Salvi
2002-05-22 0:03 ` Gérard Roudier
@ 2002-05-22 7:49 ` Fabien Salvi
2002-05-22 17:03 ` Patrick Mansfield
1 sibling, 1 reply; 9+ messages in thread
From: Fabien Salvi @ 2002-05-22 7:49 UTC (permalink / raw)
To: linux-scsi; +Cc: Lorraine Suschetet
Fabien Salvi wrote:
>
> Hello, I have problem when using the lk 2.4
>
> My system :
> - A bi-pentium II 450 processor with 1 GB RAM
> - Symbios/LSILogic SCSI card NCR 53c895
> - external Mylex DAC960SX RAID Controller (Ultra2 scsi) in a Siemens
> enclosure
>
> 1) With kernel 2.2 (exactly 2.2.19, but it's the same through 2.2.9 to
> 2.2.19), I have no problems, my disks are visible without problems :
>
> May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 8,
> function 0
> May 17 16:22:28 node01 kernel: sym53c8xx: 53c876 detected with Symbios
> NVRAM
> May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 8,
> function 1
> May 17 16:22:28 node01 kernel: sym53c8xx: 53c876 detected with Symbios
> NVRAM
> May 17 16:22:28 node01 kernel: sym53c8xx: at PCI bus 2, device 1,
> function 0
> May 17 16:22:28 node01 kernel: sym53c8xx: 53c895 detected with Symbios
> NVRAM
> May 17 16:22:28 node01 kernel: sym53c876-0: rev 0x14 on pci bus 2 device
> 8 function 0 irq 15
> May 17 16:22:28 node01 kernel: sym53c876-0: Symbios format NVRAM, ID 7,
> Fast-20, Parity Checking
> May 17 16:22:28 node01 kernel: sym53c876-0: on-chip RAM at 0xf4202000
> May 17 16:22:28 node01 kernel: sym53c876-0: restart (scsi reset).
> May 17 16:22:28 node01 kernel: sym53c876-0: Downloading SCSI SCRIPTS.
> May 17 16:22:28 node01 kernel: sym53c876-1: rev 0x14 on pci bus 2 device
> 8 function 1 irq 5
> May 17 16:22:28 node01 kernel: sym53c876-1: Symbios format NVRAM, ID 7,
> Fast-20, Parity Checking
> May 17 16:22:28 node01 kernel: sym53c876-1: on-chip RAM at 0xf4203000
> May 17 16:22:28 node01 kernel: sym53c876-1: restart (scsi reset).
> May 17 16:22:28 node01 kernel: sym53c876-1: Downloading SCSI SCRIPTS.
> May 17 16:22:28 node01 kernel: sym53c895-2: rev 0x1 on pci bus 2 device
> 1 function 0 irq 10
> May 17 16:22:28 node01 kernel: sym53c895-2: Symbios format NVRAM, ID 7,
> Fast-40, Parity Checking
> May 17 16:22:28 node01 kernel: sym53c895-2: on-chip RAM at 0xf4201000
> May 17 16:22:28 node01 kernel: sym53c895-2: restart (scsi reset).
> May 17 16:22:28 node01 kernel: sym53c895-2: Downloading SCSI SCRIPTS.
> May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 8,
> function 0
> May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2400[0..127] is in
> use
> May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 8,
> function 1
> May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2800[0..127] is in
> use
> May 17 16:22:28 node01 kernel: ncr53c8xx: at PCI bus 2, device 1,
> function 0
> May 17 16:22:28 node01 kernel: ncr53c8xx: IO region 0x2000[0..127] is in
> use
> May 17 16:22:28 node01 kernel: scsi0 : sym53c8xx-1.7.1-20000726
> May 17 16:22:28 node01 kernel: scsi1 : sym53c8xx-1.7.1-20000726
> May 17 16:22:28 node01 kernel: scsi2 : sym53c8xx-1.7.1-20000726
> May 17 16:22:28 node01 kernel: scsi : 3 hosts.
> May 17 16:22:28 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:22:28 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi disk sda at scsi0, channel
> 0, id 0, lun 0
> May 17 16:22:28 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:22:28 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi disk sdb at scsi0, channel
> 0, id 0, lun 1
> May 17 16:22:28 node01 kernel: sym53c876-0-<0,0>: tagged command queue
> depth set to 8
> May 17 16:22:28 node01 kernel: sym53c876-0-<0,1>: tagged command queue
> depth set to 8
> May 17 16:22:28 node01 kernel: Vendor: NEC Model: CD-ROM
> DRIVE:466 Rev: 1.17
> May 17 16:22:28 node01 kernel: Type:
> CD-ROM ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi CD-ROM sr0 at scsi2,
> channel 0, id 5, lun 0
> May 17 16:22:28 node01 kernel: Vendor: SIEMENS Model: STM/L
> S1 Rev: 4.1b
> May 17 16:22:28 node01 kernel: Type:
> Processor ANSI SCSI revision: 02
> May 17 16:22:28 node01 kernel: Detected scsi generic sg3 at scsi2,
> channel 0, id 8, lun 0
> May 17 16:22:28 node01 kernel: scsi : detected 4 SCSI generics 1 SCSI
> cdrom 2 SCSI disks total.
> May 17 16:22:28 node01 kernel: sym53c895-2-<5,*>: FAST-20 SCSI 20.0 MB/s
> (50 ns, offset 16)
> May 17 16:22:28 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
> xa/form2 cdda tray
> May 17 16:22:28 node01 kernel: Uniform CD-ROM driver Revision: 3.11
> May 17 16:22:28 node01 kernel: sym53c876-0-<0,*>: FAST-20 SCSI 20.0 MB/s
> (50 ns, offset 16)
> May 17 16:22:28 node01 kernel: SCSI device sda: hdwr sector= 512 bytes.
> Sectors= 17776640 [8680 MB] [8.7 GB]
> May 17 16:22:28 node01 kernel: SCSI device sdb: hdwr sector= 512 bytes.
> Sectors= 17776640 [8680 MB] [8.7 GB]
>
> It founds the real 2 disks exporting from the RAID controller (in fact
> 2*2 disks in RAID 1)
>
> 2) with 2.4.18 kernel, I've got this :
> May 17 16:19:36 node01 kernel: sym0: <875> rev 0x14 on pci bus 2 device
> 8 function 0 irq 15
> May 17 16:19:36 node01 kernel: sym0: Symbios NVRAM, ID 7, Fast-20, HVD,
> parity checking
> May 17 16:19:36 node01 kernel: sym0: open drain IRQ line driver, using
> on-chip SRAM
> May 17 16:19:36 node01 kernel: sym0: using LOAD/STORE-based firmware.
> May 17 16:19:36 node01 kernel: sym0: SCSI BUS has been reset.
> May 17 16:19:36 node01 kernel: sym1: <875> rev 0x14 on pci bus 2 device
> 8 function 1 irq 5
> May 17 16:19:36 node01 kernel: sym1: Symbios NVRAM, ID 7, Fast-20, HVD,
> parity checking
> May 17 16:19:36 node01 kernel: sym1: open drain IRQ line driver, using
> on-chip SRAM
> May 17 16:19:36 node01 kernel: sym1: using LOAD/STORE-based firmware.
> May 17 16:19:36 node01 kernel: sym1: SCSI BUS has been reset.
> May 17 16:19:36 node01 kernel: sym2: <895> rev 0x1 on pci bus 2 device 1
> function 0 irq 10
> May 17 16:19:36 node01 kernel: sym2: Symbios NVRAM, ID 7, Fast-40, LVD,
> parity checking
> May 17 16:19:36 node01 kernel: sym2: open drain IRQ line driver, using
> on-chip SRAM
> May 17 16:19:36 node01 kernel: sym2: using LOAD/STORE-based firmware.
> May 17 16:19:36 node01 kernel: sym2: SCSI BUS has been reset.
> May 17 16:19:36 node01 kernel: scsi0 : sym-2.1.17a
> May 17 16:19:36 node01 kernel: scsi1 : sym-2.1.17a
> May 17 16:19:36 node01 kernel: scsi2 : sym-2.1.17a
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: MYLEX Model: DAC960SX
> 8680T1 Rev: 1339
> May 17 16:19:36 node01 kernel: Type:
> Direct-Access ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: sym0:0:0: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:1: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:2: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:3: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:4: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:5: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:6: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: sym0:0:7: tagged command queuing enabled,
> command queue depth 16.
> May 17 16:19:36 node01 kernel: Vendor: NEC Model: CD-ROM
> DRIVE:466 Rev: 1.17
> May 17 16:19:36 node01 kernel: Type:
> CD-ROM ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Vendor: SIEMENS Model: STM/L
> S1 Rev: 4.1b
> May 17 16:19:36 node01 kernel: Type:
> Processor ANSI SCSI revision: 02
> May 17 16:19:36 node01 kernel: Attached scsi disk sda at scsi0, channel
> 0, id 0, lun 0
> May 17 16:19:36 node01 kernel: Attached scsi disk sdb at scsi0, channel
> 0, id 0, lun 1
> May 17 16:19:36 node01 kernel: Attached scsi disk sdc at scsi0, channel
> 0, id 0, lun 2
> May 17 16:19:36 node01 kernel: Attached scsi disk sdd at scsi0, channel
> 0, id 0, lun 3
> May 17 16:19:36 node01 kernel: Attached scsi disk sde at scsi0, channel
> 0, id 0, lun 4
> May 17 16:19:36 node01 kernel: Attached scsi disk sdf at scsi0, channel
> 0, id 0, lun 5
> May 17 16:19:36 node01 kernel: Attached scsi disk sdg at scsi0, channel
> 0, id 0, lun 6
> May 17 16:19:36 node01 kernel: Attached scsi disk sdh at scsi0, channel
> 0, id 0, lun 7
> May 17 16:19:36 node01 kernel: Attached scsi CD-ROM sr0 at scsi2,
> channel 0, id 5, lun 0
> May 17 16:19:36 node01 kernel: sym2:5: FAST-20 SCSI 20.0 MB/s ST (50.0
> ns, offset 16)
> May 17 16:19:36 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
> xa/form2 cdda tray
> May 17 16:19:36 node01 kernel: Uniform CD-ROM driver Revision: 3.12
> May 17 16:19:36 node01 kernel: sym0:0: FAST-20 SCSI 20.0 MB/s ST (50.0
> ns, offset 16)
> May 17 16:19:36 node01 kernel: SCSI device sda: 17776640 512-byte hdwr
> sectors (9102 MB)
> May 17 16:19:36 node01 kernel: Partition check:
> May 17 16:19:36 node01 kernel: sda: sda1 sda2 sda3 sda4
> May 17 16:19:36 node01 kernel: SCSI device sdb: 17776640 512-byte hdwr
> sectors (9102 MB)
> May 17 16:19:36 node01 kernel: sdb: sdb1
>
> Like you can see, it founds 8 disks !
> I tried to increase max_scsi_luns to 64 to see if it will find as many
> disks as luns, but it does not go after lun7 ==> 8 disks
>
> There are 3 drivers in linux kernel 2.4.18 that supports may SCSI HBA
> (sym53c8xx,sym53c8xx_2 and ncr53c8xx) but I have always the same
> results...
>
> Infortunately, I can't make tests with other cards, because I don't have
> them !
> (scsi hvd connectors).
>
> Well, I don't know why the lk founds as many disks...
>
> What do you think about it ?
> Do you have any idea ?
>
> Thanks in advance for your help !
Gérard and Doug, thanks for your help.
But, in fact, after re-reading my email, I've seen it's confusing
because I didn't explain correctly the problem.
The lk 2.2 has the good comportment : it only finds the 2 disks.
And, that's ok, I have really only 2 disks to be seen.
The problem is with the 2.4 kernel that finds 8 disks but it should only
see 2 disks, because there is only 2 disks !
The other disks are not accessible :
$fdisk /dev/sdc
Unable to open /dev/sdc
It's the same from sdc to sdh...
I've tried in the 2.4 kernel to increase the max_scsi_luns because I
thought lk may find as disks as many luns I have, but it's not the case
: it don't find more than 8 disks (maybe this is reassuring...).
So here is the problem : the lk 2.4 finds more disks than I have !
Sorry about the confusing...
Thanks in advance for your help !
-------------
Fabien SALVI Centre de Ressources Informatiques
Archamps, France -- http://www.cri74.org
PingOO GNU/linux distribution : http://www.pingoo.org
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Pb with external RAID controller in lk 2.4
2002-05-22 7:49 ` Fabien Salvi
@ 2002-05-22 17:03 ` Patrick Mansfield
2002-05-23 9:01 ` Fabien Salvi
2002-05-24 17:17 ` Kurt Garloff
0 siblings, 2 replies; 9+ messages in thread
From: Patrick Mansfield @ 2002-05-22 17:03 UTC (permalink / raw)
To: Fabien Salvi; +Cc: linux-scsi, Lorraine Suschetet
On Wed, May 22, 2002 at 09:49:01AM +0200, Fabien Salvi wrote:
> Fabien Salvi wrote:
> > May 17 16:19:36 node01 kernel: Attached scsi disk sda at scsi0, channel
> > 0, id 0, lun 0
> > May 17 16:19:36 node01 kernel: Attached scsi disk sdb at scsi0, channel
> > 0, id 0, lun 1
> > May 17 16:19:36 node01 kernel: Attached scsi disk sdc at scsi0, channel
> > 0, id 0, lun 2
> > May 17 16:19:36 node01 kernel: Attached scsi disk sdd at scsi0, channel
> > 0, id 0, lun 3
> > May 17 16:19:36 node01 kernel: Attached scsi disk sde at scsi0, channel
> > 0, id 0, lun 4
> > May 17 16:19:36 node01 kernel: Attached scsi disk sdf at scsi0, channel
> > 0, id 0, lun 5
> > May 17 16:19:36 node01 kernel: Attached scsi disk sdg at scsi0, channel
> > 0, id 0, lun 6
> > May 17 16:19:36 node01 kernel: Attached scsi disk sdh at scsi0, channel
> > 0, id 0, lun 7
> > May 17 16:19:36 node01 kernel: Attached scsi CD-ROM sr0 at scsi2,
> > channel 0, id 5, lun 0
> > May 17 16:19:36 node01 kernel: sym2:5: FAST-20 SCSI 20.0 MB/s ST (50.0
> > ns, offset 16)
> > May 17 16:19:36 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
> > xa/form2 cdda tray
> > May 17 16:19:36 node01 kernel: Uniform CD-ROM driver Revision: 3.12
> > May 17 16:19:36 node01 kernel: sym0:0: FAST-20 SCSI 20.0 MB/s ST (50.0
> > ns, offset 16)
> > May 17 16:19:36 node01 kernel: SCSI device sda: 17776640 512-byte hdwr
> > sectors (9102 MB)
> > May 17 16:19:36 node01 kernel: Partition check:
> > May 17 16:19:36 node01 kernel: sda: sda1 sda2 sda3 sda4
> > May 17 16:19:36 node01 kernel: SCSI device sdb: 17776640 512-byte hdwr
> > sectors (9102 MB)
> > May 17 16:19:36 node01 kernel: sdb: sdb1
> >
> > Like you can see, it founds 8 disks !
> > I tried to increase max_scsi_luns to 64 to see if it will find as many
> > disks as luns, but it does not go after lun7 ==> 8 disks
> >
> Gérard and Doug, thanks for your help.
>
> But, in fact, after re-reading my email, I've seen it's confusing
> because I didn't explain correctly the problem.
>
> The lk 2.2 has the good comportment : it only finds the 2 disks.
> And, that's ok, I have really only 2 disks to be seen.
>
> The problem is with the 2.4 kernel that finds 8 disks but it should only
> see 2 disks, because there is only 2 disks !
>
> The other disks are not accessible :
> $fdisk /dev/sdc
>
> Unable to open /dev/sdc
>
> It's the same from sdc to sdh...
>
>
> I've tried in the 2.4 kernel to increase the max_scsi_luns because I
> thought lk may find as disks as many luns I have, but it's not the case
> : it don't find more than 8 disks (maybe this is reassuring...).
>
> So here is the problem : the lk 2.4 finds more disks than I have !
The 2.4 kernel won't scan past LUN 7 for SCSI-2 devices - you can try
modifying the code and set the max to 31 in scsi_scan.c.
The device is probably setting the peripheral-qualifier (PQ) such that the
scan continues but the device is marked offline, this is just annoying
if do not have a lot of them. In scsi_scan.c:
/* Use the peripheral qualifier field to determine online/offline */
if (((scsi_result[0] >> 5) & 7) == 1) SDpnt->online = FALSE;
else SDpnt->online = TRUE;
The above means that sd will attach to the device, but won't try to read
capacity etc, and an open of the device will fail. Redhat kernels have
some changes to avoid this problem, there was also a PQ patch posted
some time ago (it would make sense to put it into 2.5, especially now that
the inquiry data is retained, and avoid setting online to FALSE).
There is also some odd case (AFAIR when initializing sd after the adapter has
been loaded and scanned the devices) where the online gets reset to TRUE
and causes sd.c to fail trying to read the non-existent LUN.
-- Patrick Mansfield
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Pb with external RAID controller in lk 2.4
2002-05-22 17:03 ` Patrick Mansfield
@ 2002-05-23 9:01 ` Fabien Salvi
2002-05-24 17:17 ` Kurt Garloff
1 sibling, 0 replies; 9+ messages in thread
From: Fabien Salvi @ 2002-05-23 9:01 UTC (permalink / raw)
To: Patrick Mansfield; +Cc: linux-scsi, Lorraine Suschetet
Patrick Mansfield wrote:
>
> On Wed, May 22, 2002 at 09:49:01AM +0200, Fabien Salvi wrote:
> > Fabien Salvi wrote:
>
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sda at scsi0, channel
> > > 0, id 0, lun 0
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdb at scsi0, channel
> > > 0, id 0, lun 1
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdc at scsi0, channel
> > > 0, id 0, lun 2
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdd at scsi0, channel
> > > 0, id 0, lun 3
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sde at scsi0, channel
> > > 0, id 0, lun 4
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdf at scsi0, channel
> > > 0, id 0, lun 5
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdg at scsi0, channel
> > > 0, id 0, lun 6
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdh at scsi0, channel
> > > 0, id 0, lun 7
> > > May 17 16:19:36 node01 kernel: Attached scsi CD-ROM sr0 at scsi2,
> > > channel 0, id 5, lun 0
> > > May 17 16:19:36 node01 kernel: sym2:5: FAST-20 SCSI 20.0 MB/s ST (50.0
> > > ns, offset 16)
> > > May 17 16:19:36 node01 kernel: sr0: scsi3-mmc drive: 17x/40x cd/rw
> > > xa/form2 cdda tray
> > > May 17 16:19:36 node01 kernel: Uniform CD-ROM driver Revision: 3.12
> > > May 17 16:19:36 node01 kernel: sym0:0: FAST-20 SCSI 20.0 MB/s ST (50.0
> > > ns, offset 16)
> > > May 17 16:19:36 node01 kernel: SCSI device sda: 17776640 512-byte hdwr
> > > sectors (9102 MB)
> > > May 17 16:19:36 node01 kernel: Partition check:
> > > May 17 16:19:36 node01 kernel: sda: sda1 sda2 sda3 sda4
> > > May 17 16:19:36 node01 kernel: SCSI device sdb: 17776640 512-byte hdwr
> > > sectors (9102 MB)
> > > May 17 16:19:36 node01 kernel: sdb: sdb1
> > >
> > > Like you can see, it founds 8 disks !
> > > I tried to increase max_scsi_luns to 64 to see if it will find as many
> > > disks as luns, but it does not go after lun7 ==> 8 disks
> > >
>
> > Gérard and Doug, thanks for your help.
> >
> > But, in fact, after re-reading my email, I've seen it's confusing
> > because I didn't explain correctly the problem.
> >
> > The lk 2.2 has the good comportment : it only finds the 2 disks.
> > And, that's ok, I have really only 2 disks to be seen.
> >
> > The problem is with the 2.4 kernel that finds 8 disks but it should only
> > see 2 disks, because there is only 2 disks !
> >
> > The other disks are not accessible :
> > $fdisk /dev/sdc
> >
> > Unable to open /dev/sdc
> >
> > It's the same from sdc to sdh...
> >
> >
> > I've tried in the 2.4 kernel to increase the max_scsi_luns because I
> > thought lk may find as disks as many luns I have, but it's not the case
> > : it don't find more than 8 disks (maybe this is reassuring...).
> >
> > So here is the problem : the lk 2.4 finds more disks than I have !
>
> The 2.4 kernel won't scan past LUN 7 for SCSI-2 devices - you can try
> modifying the code and set the max to 31 in scsi_scan.c.
>
> The device is probably setting the peripheral-qualifier (PQ) such that the
> scan continues but the device is marked offline, this is just annoying
> if do not have a lot of them. In scsi_scan.c:
>
> /* Use the peripheral qualifier field to determine online/offline */
> if (((scsi_result[0] >> 5) & 7) == 1) SDpnt->online = FALSE;
> else SDpnt->online = TRUE;
>
> The above means that sd will attach to the device, but won't try to read
> capacity etc, and an open of the device will fail. Redhat kernels have
> some changes to avoid this problem, there was also a PQ patch posted
> some time ago (it would make sense to put it into 2.5, especially now that
> the inquiry data is retained, and avoid setting online to FALSE).
>
> There is also some odd case (AFAIR when initializing sd after the adapter has
> been loaded and scanned the devices) where the online gets reset to TRUE
> and causes sd.c to fail trying to read the non-existent LUN.
Thanks for your help Patrick, I think it's the solution.
Well, like I have not so many disks found, I will let them in this
state...
-------------
Fabien SALVI Centre de Ressources Informatiques
Archamps, France -- http://www.cri74.org
PingOO GNU/linux distribution : http://www.pingoo.org
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: Pb with external RAID controller in lk 2.4
2002-05-22 17:03 ` Patrick Mansfield
2002-05-23 9:01 ` Fabien Salvi
@ 2002-05-24 17:17 ` Kurt Garloff
2002-05-24 17:44 ` Patrick Mansfield
1 sibling, 1 reply; 9+ messages in thread
From: Kurt Garloff @ 2002-05-24 17:17 UTC (permalink / raw)
To: Patrick Mansfield; +Cc: Fabien Salvi, linux-scsi, Lorraine Suschetet
[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]
Hi Patrick,
On Wed, May 22, 2002 at 10:03:39AM -0700, Patrick Mansfield wrote:
> On Wed, May 22, 2002 at 09:49:01AM +0200, Fabien Salvi wrote:
> > Fabien Salvi wrote:
>
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sda at scsi0, channel
> > > 0, id 0, lun 0
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdb at scsi0, channel
> > > 0, id 0, lun 1
[...]
> > > May 17 16:19:36 node01 kernel: Attached scsi disk sdh at scsi0, channel
> > > 0, id 0, lun 7
> > > May 17 16:19:36 node01 kernel: Attached scsi CD-ROM sr0 at scsi2,
> > > channel 0, id 5, lun 0
[...]
> > > Like you can see, it founds 8 disks !
[...]
> > I've tried in the 2.4 kernel to increase the max_scsi_luns because I
> > thought lk may find as disks as many luns I have, but it's not the case
> > : it don't find more than 8 disks (maybe this is reassuring...).
> >
> > So here is the problem : the lk 2.4 finds more disks than I have !
>
> The 2.4 kernel won't scan past LUN 7 for SCSI-2 devices - you can try
> modifying the code and set the max to 31 in scsi_scan.c.
If you have a FC device (or whatever device that supports LUNs > 7) that
reports as SCSI-2, you can flag it with BLIST_LARGELUN in scsi_scan.c
to get it treated as SCSI-3.
(New in 2.4.18)
> The device is probably setting the peripheral-qualifier (PQ) such that the
> scan continues but the device is marked offline, this is just annoying
> if do not have a lot of them. In scsi_scan.c:
>
> /* Use the peripheral qualifier field to determine online/offline */
> if (((scsi_result[0] >> 5) & 7) == 1) SDpnt->online = FALSE;
> else SDpnt->online = TRUE;
Those fields should not be set by the device, IMHO.
Or has their meaning changed for SCSI-3 devs? Then the appropriate check
should be added to the code.
But actually the problem is different: Too many LUNs where detected :-(
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE Linux AG, Nuernberg, DE SCSI, Security
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Pb with external RAID controller in lk 2.4
2002-05-24 17:17 ` Kurt Garloff
@ 2002-05-24 17:44 ` Patrick Mansfield
2002-05-24 17:55 ` Kurt Garloff
0 siblings, 1 reply; 9+ messages in thread
From: Patrick Mansfield @ 2002-05-24 17:44 UTC (permalink / raw)
To: Kurt Garloff, Patrick Mansfield, Fabien Salvi, linux-scsi,
Lorraine Suschetet
On Fri, May 24, 2002 at 07:17:33PM +0200, Kurt Garloff wrote:
> Hi Patrick,
>
> On Wed, May 22, 2002 at 10:03:39AM -0700, Patrick Mansfield wrote:
> > The 2.4 kernel won't scan past LUN 7 for SCSI-2 devices - you can try
> > modifying the code and set the max to 31 in scsi_scan.c.
>
> If you have a FC device (or whatever device that supports LUNs > 7) that
> reports as SCSI-2, you can flag it with BLIST_LARGELUN in scsi_scan.c
> to get it treated as SCSI-3.
> (New in 2.4.18)
I don't see that in 2.4.18, is it in a 2.4.19-pre? (I can't get to
any kernel.org or a mirror right now.)
> > /* Use the peripheral qualifier field to determine online/offline */
> > if (((scsi_result[0] >> 5) & 7) == 1) SDpnt->online = FALSE;
> > else SDpnt->online = TRUE;
> Those fields should not be set by the device, IMHO.
> Or has their meaning changed for SCSI-3 devs? Then the appropriate check
> should be added to the code.
I don't think anything has changed, SCSI-3 for a peripheral qualifier
of 001b says:
The device server is capable of supporting the specified peripheral device
type on this logical unit. However, the physical device is not currently
connected to this logical unit.
So it seems reasonable to set it to 1. For many disk arrays, this value
can be modified - the pq or byte one of the INQUIRY result for LUNs with
with no storage.
-- Patrick Mansfield
>
> > The device is probably setting the peripheral-qualifier (PQ) such that the
> > scan continues but the device is marked offline, this is just annoying
> > if do not have a lot of them. In scsi_scan.c:
> >
>
> But actually the problem is different: Too many LUNs where detected :-(
>
> Regards,
> --
> Kurt Garloff <garloff@suse.de> Eindhoven, NL
> GPG key: See mail header, key servers Linux kernel development
> SuSE Linux AG, Nuernberg, DE SCSI, Security
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Pb with external RAID controller in lk 2.4
2002-05-24 17:44 ` Patrick Mansfield
@ 2002-05-24 17:55 ` Kurt Garloff
0 siblings, 0 replies; 9+ messages in thread
From: Kurt Garloff @ 2002-05-24 17:55 UTC (permalink / raw)
To: Patrick Mansfield; +Cc: Fabien Salvi, linux-scsi, Lorraine Suschetet
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Hi Patrick,
On Fri, May 24, 2002 at 10:44:50AM -0700, Patrick Mansfield wrote:
> On Fri, May 24, 2002 at 07:17:33PM +0200, Kurt Garloff wrote:
> > If you have a FC device (or whatever device that supports LUNs > 7) that
> > reports as SCSI-2, you can flag it with BLIST_LARGELUN in scsi_scan.c
> > to get it treated as SCSI-3.
> > (New in 2.4.18)
>
> I don't see that in 2.4.18, is it in a 2.4.19-pre? (I can't get to
> any kernel.org or a mirror right now.)
You're right. Sorry! When I submitted to Marcelo for 2.4.18 inclusion it was
too late already. But it was in Alans tree for some time and got merged by
Marcelo in 2.4.19pre, indeed.
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE Linux AG, Nuernberg, DE SCSI, Security
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2002-05-24 17:55 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-21 17:28 Pb with external RAID controller in lk 2.4 Fabien Salvi
2002-05-22 0:03 ` Gérard Roudier
2002-05-22 1:03 ` Douglas Gilbert
2002-05-22 7:49 ` Fabien Salvi
2002-05-22 17:03 ` Patrick Mansfield
2002-05-23 9:01 ` Fabien Salvi
2002-05-24 17:17 ` Kurt Garloff
2002-05-24 17:44 ` Patrick Mansfield
2002-05-24 17:55 ` Kurt Garloff
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox