On 06/24/2010 09:10 PM, EK Shen wrote:
Hi!
I found some difference between the log files of x86 and kirkwood.

x86:
iscsid: sysfs_attr_get_value: open '/class/scsi_host/
host8'/'proc_name'
iscsid: sysfs_attr_get_value: new uncached attribute '/sys/class/
scsi_host/host8/proc_name'
iscsid: sysfs_attr_get_value: add to cache '/sys/class/scsi_host/host8/
proc_name'
iscsid: sysfs_attr_get_value: cache '/sys/class/scsi_host/host8/
proc_name' with attribute value 'iscsi_tcp'

kirkwood:
iscsid: sysfs_attr_get_value: open '/class/scsi_host/
host0'/'proc_name'
iscsid: sysfs_attr_get_value: new uncached attribute '/sys/class/
scsi_host/host0/proc_name'
iscsid: sysfs_attr_get_value: add to cache '/sys/class/scsi_host/host0/
proc_name'
iscsid: sysfs_attr_get_value: cache '/sys/class/scsi_host/host0/
proc_name' with attribute value 'mvSata'


Could you send all the log output? It could be that iscsid/iscsiadm messed up and asked for the wrong host/sessions and so instead of getting one with proc_name=tcp we asked for one with mvSata. Or it could just be a part of iscsid/iscsiadm that is searching for host's with proc_name=tcp.

--
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/open-iscsi?hl=en.

Reply via email to