Re: Information about iSCSI pings that almost timed out
On Thu, Nov 19, 2009 at 10:02 PM, Mike Christie micha...@cs.wisc.edu wrote: Ulrich Windl wrote: On 19 Nov 2009 at 11:07, Erez Zilber wrote: On Thu, Nov 19, 2009 at 9:38 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Hi! Wouldn't it be more obvious to calculate the average delay to a ping request? (Possibly exponential average as for the system loads) (min and Max would be good as well, but standard deviation probably requires use of the FPU, so that's not possible in kernel modules (AFAIK)). It's in userspace, so (almost) everything is possible. It's nice to have counters, average delay etc, but I want to be able to know exactly when bad things almost happened (i.e. timeout almost expired). Counters/average delay will not help me. I thought you want to tune the timeouts. So if properly tuned, the kernel will log when when your measurements are unusual (i.e. timeout exceeded). I think that is what I wanted. I think Erez wants something a little different, right Erez? I think that it would be nice if we had both: 1. The average delay of a ping request. 2. A list of ping requests that almost timed out with some helpful info (when was the ping sent and how much time until we got a response). With this information, you can understand and debug the whole system: you can check your target and see what caused it to be so slow on that specific time, you can see if your network was very busy during that time etc. Erez -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=.
Re: missing references to strlcpy and strlcat when trying to compile utils/fwparam_ibft
NutStation wrote: Hi! I am in the process of setting up my first iscsi boot environment and i am using open-scsi as the initiator for my nodes. I am followiing this excellent tute: http://www.etherboot.org/wiki/sanboot/debian_etch_iscsi As the tute states, the fwparam_ibft executable is not part of debian install, and so I set forth to compile it manually per the instructions. However it didn't quite work out as I had hoped. First I had alot of errors like these: /root/open-iscsi-2.0-871/utils/fwparam_ibft/fwparam_ibft.c:395: undefined reference to `strlcpy' I fixed that by copying the strlcpy and strlcat implementations from postgreSQL from here: http://doxygen.postgresql.org/strlcat_8c-source.html into a new file strl.c and incorporating that into the Makefile However when I try to create the fwparam_ibft executalbe that the original tute talks about after meding the strl* problem, it now complains that there is no main function. And indeed after grep'ing the whole dir there are no main functions to be seen for fwparam_ibft This leads me to the following question: 1.How can i obtain the fwparam_ibft binary or the current equivalent/ replacement? If you just do make user or make from the top level of the tarball then it should all build ok. There is no fwparam_ibft program. Instead just run iscsiadm in fw mode. log into targets found in fw iscsiadm -m fw -l print out the targets found in fw and create /etc/iscsi/nodes records for them iscsiadm -m discovery -t fw -P 1 print out the targets found in fw and create /etc/iscsi/nodes records for them and login iscsiadm -m discovery -t fw -P 1 -l 2.What changes must be made to the build instructions and the boot scripts mentioned in that tute? Are you using ibft? Thanks! -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=.
Re: Information about iSCSI pings that almost timed out
Erez Zilber wrote: On Thu, Nov 19, 2009 at 10:02 PM, Mike Christie micha...@cs.wisc.edu wrote: Ulrich Windl wrote: On 19 Nov 2009 at 11:07, Erez Zilber wrote: On Thu, Nov 19, 2009 at 9:38 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Hi! Wouldn't it be more obvious to calculate the average delay to a ping request? (Possibly exponential average as for the system loads) (min and Max would be good as well, but standard deviation probably requires use of the FPU, so that's not possible in kernel modules (AFAIK)). It's in userspace, so (almost) everything is possible. It's nice to have counters, average delay etc, but I want to be able to know exactly when bad things almost happened (i.e. timeout almost expired). Counters/average delay will not help me. I thought you want to tune the timeouts. So if properly tuned, the kernel will log when when your measurements are unusual (i.e. timeout exceeded). I think that is what I wanted. I think Erez wants something a little different, right Erez? I think that it would be nice if we had both: 1. The average delay of a ping request. 2. A list of ping requests that almost timed out with some helpful info (when was the ping sent and how much time until we got a response). With this information, you can understand and debug the whole system: you can check your target and see what caused it to be so slow on that specific time, you can see if your network was very busy during that time etc. I think this sounds good to me. -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=.
Re: missing references to strlcpy and strlcat when trying to compile utils/fwparam_ibft
I figured this out by myself after alot of anguish. It turns out fwparam_ibft has been merged into the iscsistart tool. By running iscsistart -f you get something similar but not quite the same as the result of running feparam_ibft. Hope this is useful to some other poor soul! -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=.
Re: Information about iSCSI pings that almost timed out
On Sun, Nov 22, 2009 at 10:44 PM, Mike Christie micha...@cs.wisc.edu wrote: Erez Zilber wrote: On Thu, Nov 19, 2009 at 10:02 PM, Mike Christie micha...@cs.wisc.edu wrote: Ulrich Windl wrote: On 19 Nov 2009 at 11:07, Erez Zilber wrote: On Thu, Nov 19, 2009 at 9:38 AM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote: Hi! Wouldn't it be more obvious to calculate the average delay to a ping request? (Possibly exponential average as for the system loads) (min and Max would be good as well, but standard deviation probably requires use of the FPU, so that's not possible in kernel modules (AFAIK)). It's in userspace, so (almost) everything is possible. It's nice to have counters, average delay etc, but I want to be able to know exactly when bad things almost happened (i.e. timeout almost expired). Counters/average delay will not help me. I thought you want to tune the timeouts. So if properly tuned, the kernel will log when when your measurements are unusual (i.e. timeout exceeded). I think that is what I wanted. I think Erez wants something a little different, right Erez? I think that it would be nice if we had both: 1. The average delay of a ping request. 2. A list of ping requests that almost timed out with some helpful info (when was the ping sent and how much time until we got a response). With this information, you can understand and debug the whole system: you can check your target and see what caused it to be so slow on that specific time, you can see if your network was very busy during that time etc. I think this sounds good to me. Great. I will try to send a patch soon. Erez -- You received this message because you are subscribed to the Google Groups open-iscsi group. To post to this group, send email to open-is...@googlegroups.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=.
