From: Vladislav B. <vs...@vl...> - 2006-11-30 17:05:45
|
Try with the latest SVN. I fixed there one bug, which could affect you. Vlad Shantanoo Mahajan wrote: > +++ Vladislav Bolkhovitin [24-11-06 13:58 +0300]: > | Shantanoo Mahajan wrote: > | > +++ Vladislav Bolkhovitin [23-11-06 13:20 +0300]: > | > | Hi, > | > | > | > | Check if your initiator supports that. If not, it should report that in > | > | the kernel logs. You may need to recompile the kernel there, although on > | > | 2.6 kernels usually it's sufficient to pass the appropriate parameter > | > | "max_luns" to scsi_mod module. > | > > | > My host has following configuration. > | > RHEL4 with QLA2312 on it. > | > with the following kernel boot parameters: > | > > | > kernel /vmlinuz-2.6.9-34.ELsmp ro root=/dev/VolGroup00/LogVol00 rhgb > | > quiet max_report_luns=2000 max_luns=2000 max_scsi_report_luns=2000 > | > scsi_mod.scsi_logging=448 > | > | Such command line is shot to nowhere. Parameter "max_luns" is for > | scsi_mod module, not for the kernel itself, so "scsi_mod.max_luns=2000" > | will be more correct. But I'm not sure that it works, if scsi_mod is > | built as a module. > > > Hi, > > My current configuration is as follows: > OS: SuSe 9 Enterprise server > HBA: qlogic2312 > > After changing parameters max_luns and max_report_luns in > modprobe.conf and as boot parameters I am not able to see more luns. > > The error message I am getting is similar to: > scsi: host 3 channel 0 id 0 lun512 has a LUN larger than allowed by the host adapter > > Could you let me know your OS/HBA configuration so I can try this > using that. > > Regards, > Shantanoo > |