On Mon, 2005-04-11 at 12:52 +0100, Christoph Hellwig wrote:
> James once had a proposal where the scsi_host can link to the module in
> sysfs, which is the right thing and needed for other things like mkinitrd
> aswell.
The code is actually in. Taking advantage of it is slightly more
complex than
On Fri, Apr 08, 2005 at 06:03:16PM +1000, Douglas Gilbert wrote:
> >The real problem is that someone decided to export the proc_name in sysfs.
> >It's supposed to be only procfs-specific but someone violated that rule.
>
> Forget the "proc_" part. It is effectivel
d to replace the confusing "proc" prefix.
The real problem is that someone decided to export the proc_name in sysfs.
It's supposed to be only procfs-specific but someone violated that rule.
Forget the "proc_" part. It is effectively the lld_name.
Allowing the LLD to name its
Hi,
Patrick Mansfield a écrit :
On Thu, Apr 07, 2005 at 08:35:16AM +0200, Frederic TEMPORELLI wrote:
Hi,
Sorry, no such "driver" directory in /sys/class/scsi_host/hostX/
Doug answered that.
thx, I've just try the script and it works...
(mea culpa, I should have look in details to the symlinks)
W
proc_name field has to be kept initialized
> and/or something has to be changed to replace the confusing "proc" prefix.
The real problem is that someone decided to export the proc_name in sysfs.
It's supposed to be only procfs-specific but someone violated that rule.
Not sure h
On Thu, Apr 07, 2005 at 08:35:16AM +0200, Frederic TEMPORELLI wrote:
> Hi,
>
>
> Sorry, no such "driver" directory in /sys/class/scsi_host/hostX/
Doug answered that.
> >>Why do you need it?
If you answer the above you might get better/other suggestions.
-- Patrick Mansfield
-
To unsubscribe f
On Thu, Apr 07, 2005 at 11:06:03AM +1000, Douglas Gilbert wrote:
> Patrick Mansfield wrote:
> >On Wed, Apr 06, 2005 at 01:40:04PM +0200, Frederic TEMPORELLI wrote:
> >
> >
> >>2/ now, how can we get the adapter module name from sysfs ?
> >
> >
> >Why do you need it?
> Patrick,
> lsscsi currently
Frederic TEMPORELLI wrote:
Hi,
Sorry, no such "driver" directory in /sys/class/scsi_host/hostX/
(checked: Emulex "lpfc" 8.0.24 and LSI "mptscsih" 3.01.18)
I may have missed the point here. Are you talking about
Patrick's shell script? It sort of works for me. Example:
$ ./scan_hosts.sh
/sys/class/s
Hi,
Sorry, no such "driver" directory in /sys/class/scsi_host/hostX/
(checked: Emulex "lpfc" 8.0.24 and LSI "mptscsih" 3.01.18)
note: there's also a "proc_name" interface for LSI "mtpscsih", located in
/sys/class/scsi_host/hostX/, which is reporting "mptscsih" string.
Any other ideas ?
Best regar
Patrick Mansfield wrote:
On Wed, Apr 06, 2005 at 01:40:04PM +0200, Frederic TEMPORELLI wrote:
2/ now, how can we get the adapter module name from sysfs ?
Why do you need it?
Anyway, try lsscsi, it walks the sysfs tree:
[elm3b79 patman]$ lsscsi -H
[0]qla1280
[1]qla1280
[2]qla2xxx
[3]
On Wed, Apr 06, 2005 at 01:40:04PM +0200, Frederic TEMPORELLI wrote:
> 2/ now, how can we get the adapter module name from sysfs ?
Why do you need it?
Anyway, try lsscsi, it walks the sysfs tree:
[elm3b79 patman]$ lsscsi -H
[0]qla1280
[1]qla1280
[2]qla2xxx
[3]qla2xxx
Or, scrip
Hello,
We are using HBAs modules names from "proc_name" interface in sysfs:
/sys/class/scsi_host/hostX/proc_name.
But with new Emulex drivers (8.0.21 and +), proc_name is reporting
(previous drivers were reporting "lpfc").
=> In the driver code, .proc_name field from scsi_host_template structure
12 matches
Mail list logo
