Re: ScsiSata Inquiry tool for linux

2006-10-15 Thread guy keren
On Sat, 14 Oct 2006, Amos Shapira wrote: On 14/10/06, guy keren [EMAIL PROTECTED] wrote: i'm afraid that a simple scsi rescan will not work - there's no such thing in kernel 2.4 (neither in kernel 2.6, before 2.6.12). we had to work for a while in order to get a rescan to work, and

Re: ScsiSata Inquiry tool for linux

2006-10-15 Thread Amos Shapira
On 15/10/06, guy keren [EMAIL PROTECTED] wrote: i didn't try that on a machine connected to a SAN yet (or, in fact, withany SCSI HBA), but i think it only reports to you, the user, about theSCSI targets (LUNs?) it sees - it does not make new SCSI disks appear on the system.Was this (making these

Re: ScsiSata Inquiry tool for linux

2006-10-14 Thread Amos Shapira
On 14/10/06, guy keren [EMAIL PROTECTED] wrote: i'm afraid that a simple scsi rescan will not work - there's no suchthing in kernel 2.4 (neither in kernel 2.6, before 2.6.12). we had towork for a while in order to get a rescan to work, and even then it's not a general-purpose solution.What about

Re: ScsiSata Inquiry tool for linux

2006-10-13 Thread guy keren
[since you're a top-poster, i'll top-post too ;)] in kernel 2.4, for SCSI disks, there is support for at most 16 * 16 = 256 devices. there are 16 major numbers (listed in the kernel's documentation), and for each of them, there are minors 0, 16, 32, 48 that are used for the devices (the

Re: ScsiSata Inquiry tool for linux

2006-10-13 Thread Jacob Broido
Good idea,Also, if I remmeber correctly sg3utils allows to issue a SCSI RESCAN, which I can use to overcome the 'linux kernel not being aware of new LUNs' issue.2.6.x really made things sane in this area. On 10/13/06, guy keren [EMAIL PROTECTED] wrote: [since you're a top-poster, i'll top-post too

Re: ScsiSata Inquiry tool for linux

2006-10-13 Thread guy keren
i'm afraid that a simple scsi rescan will not work - there's no such thing in kernel 2.4 (neither in kernel 2.6, before 2.6.12). we had to work for a while in order to get a rescan to work, and even then it's not a general-purpose solution. --guy On Fri, 2006-10-13 at 20:47 +0200, Jacob Broido

Re: ScsiSata Inquiry tool for linux

2006-10-13 Thread Michael Vasiliev
On Friday October 13 2006 15:59, guy keren wrote: [since you're a top-poster, i'll top-post too ;)] Ugh :[ -- Sincerely Yours, Michael Vasiliev If in physics there's something you don't understand, you can always hide behind the uncharted depths of nature. You can always blame God. You

ScsiSata Inquiry tool for linux

2006-10-12 Thread Jacob Broido
Hey, I've been looking for some time for a way to list all scsi,sata,ide devices that are currently 'seen' by the linux host. The tool should do the following: 1) Find all HBAs in the host. 2)Query each HBA (should be HBA agnostic) 3) Query each device returned by HBA query, and extract the

Re: ScsiSata Inquiry tool for linux

2006-10-12 Thread Amos Shapira
On 12/10/06, Jacob Broido [EMAIL PROTECTED] wrote: The tool should do the following: 1) Find all HBAs in the host. 2)Query each HBA (should be HBA agnostic) 3) Query each device returned by HBA query, and extract the following: size,type,vendorlshal(1)?--Amos-- Military justice is to justice what

Re: ScsiSata Inquiry tool for linux

2006-10-12 Thread Jacob Broido
Some additions... In kernels 2.6.x with sysfs, a quite simple tool can be written to extract the info mentioned below. So for 2.6.x I am covered. The question remains for 2.4.x kernels. On 10/12/06, Jacob Broido [EMAIL PROTECTED] wrote: Hey, I've been looking for some time for a way to list

Re: ScsiSata Inquiry tool for linux

2006-10-12 Thread Jacob Broido
Thanks, was familiar with it. But still, it doesnt display disk size, which I guess I will extract with blockdev --size dev On 10/12/06, Amos Shapira [EMAIL PROTECTED] wrote: On 12/10/06, Jacob Broido [EMAIL PROTECTED] wrote: The tool should do the following: 1) Find all HBAs in the host.

Re: ScsiSata Inquiry tool for linux

2006-10-12 Thread Jacob Broido
Hey, as mentioned by Amos, there is a tool called lshal, which works in 2.6.x , not sure about 2.4.x - (Any comments on this?) lshal is much more usefull than lspci and it provides more details info. The missing information from lshal is the disk size. This can be easily extracted using blockdev