On 19/02/2011 22:40, Phil Turmel wrote:
On 02/19/2011 05:30 PM, Mathias BurÃn wrote:
[...]
This is the output of your latest script on my machine. The "0:0:0"
is supposed to be the LUN, which would be ata[1, 2, 3..], no?
No. You have to look in your dmesg to match the 'ata' initialization
reports with the corresponding 'scsi' initialization reports.
dmesg |grep 'ata[0-9]\|scsi[0-9]'
Unless I missed something in sysfs that would make it easy to report
it in the script?
I don't know about easy, but there is a suggestion in the page Simon
McNair linked to earlier in this thread:
http://www.linux-archive.org/centos/316405-how-map-ata-numbers-dev-sd-numbers.html#post428370
I suspect that at the very least you'd have to check the proc_name to
see if it matched a driver which used libata before you could say the
unique_id matched the kernel's ata:N though, which is why I say it might
not be easy (well beyond me at any rate)...
Cheers,
John.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
