linux-iscsi-users — Users of Linux iSCSI driver

Re: [linux-iscsi-users] iscsid iterates through /proc/<pid>/stat looking for kernel thread called iscsi_q_NN when ...

[Michael C. <mic...@cs...>]

Did you mean to send this to the open-iscsi list or linux-scsi?

> On Mar 24, 2016, at 9:53 PM, Richard Sharpe <rea...@gm...> wrote:
> 
> Hi folks,
> 
> iscsid iterates through /proc/<pid>/stat looking for kernel threads
> called iscsiq_q_NNN and then calls setpriority on the thread found.
> 
> When you have a large number of iSCSI targets, which you can have in
> modern systems this becomes quadratic behavior.
> 
> However, in drivers/scsi/libiscsi.c:iscsi_host_alloc we see (in 3.10
> and probably later)
> 
>        if (xmit_can_sleep) {
>                snprintf(ihost->workq_name, sizeof(ihost->workq_name),
>                        "iscsi_q_%d", shost->host_no);
>                ihost->workq = create_singlethread_workqueue(ihost->workq_name);
>                if (!ihost->workq)
>                        goto free_host;
>        }
> 
> 
> what is wrong with doing something like:
> 
>              set_user_nics(ihost->workq->cpu_wq->thread, NICE_VALUE)

I think we did it in userspace because the function we needed was not exported for a while (it was exported then removed then added back or something), but yeah that is much better. If you have a patch send to linux-scsi and I will ack it for merging upstream.


> 
> after the work queue is created?
> 
> Something like that should work, I imagine, even if we have to
> communicate that value to the kernel.

Just use MIN_NICE like the other storage driver do.

Re: [linux-iscsi-users] iscsid iterates through /proc/<pid>/stat looking for kernel thread called iscsi_q_NN when ...

[Richard S. <rea...@gm...>]

On Thu, Mar 24, 2016 at 7:53 PM, Richard Sharpe
<rea...@gm...> wrote:
> Hi folks,
>
> iscsid iterates through /proc/<pid>/stat looking for kernel threads
> called iscsiq_q_NNN and then calls setpriority on the thread found.
>
> When you have a large number of iSCSI targets, which you can have in
> modern systems this becomes quadratic behavior.
>
> However, in drivers/scsi/libiscsi.c:iscsi_host_alloc we see (in 3.10
> and probably later)
>
>         if (xmit_can_sleep) {
>                 snprintf(ihost->workq_name, sizeof(ihost->workq_name),
>                         "iscsi_q_%d", shost->host_no);
>                 ihost->workq = create_singlethread_workqueue(ihost->workq_name);
>                 if (!ihost->workq)
>                         goto free_host;
>         }
>
>
> what is wrong with doing something like:
>
>               set_user_nics(ihost->workq->cpu_wq->thread, NICE_VALUE)

That should be set_user_nice.

> after the work queue is created?
>
> Something like that should work, I imagine, even if we have to
> communicate that value to the kernel.
>
> Is this something that would be useful?
>
> --
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)



-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)

[linux-iscsi-users] iscsid iterates through /proc/<pid>/stat looking for kernel thread called iscsi_q_NN when ...

[Richard S. <rea...@gm...>]

Hi folks,

iscsid iterates through /proc/<pid>/stat looking for kernel threads
called iscsiq_q_NNN and then calls setpriority on the thread found.

When you have a large number of iSCSI targets, which you can have in
modern systems this becomes quadratic behavior.

However, in drivers/scsi/libiscsi.c:iscsi_host_alloc we see (in 3.10
and probably later)

        if (xmit_can_sleep) {
                snprintf(ihost->workq_name, sizeof(ihost->workq_name),
                        "iscsi_q_%d", shost->host_no);
                ihost->workq = create_singlethread_workqueue(ihost->workq_name);
                if (!ihost->workq)
                        goto free_host;
        }


what is wrong with doing something like:

              set_user_nics(ihost->workq->cpu_wq->thread, NICE_VALUE)

after the work queue is created?

Something like that should work, I imagine, even if we have to
communicate that value to the kernel.

Is this something that would be useful?

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)

[linux-iscsi-users] LVM can not be found

[Wukongming <wu....@h3...>]

Hi, everyone.

   Have you ever happened to this issue, and how to fix it? I deployed a LVM and open-iscsi in the client and a tgt in the server. But in some circumstance LVM can't been found. Here is a steps:


1.       Stop Tgt process;

2.       The directory which a mapped device mounted is workless;

3.       Restart Tgt process, The directory is still not working;

4.       Umount the mapped virtual device, the client will blocked;

5.       Restart the client, LVM modules like pv, lv are not found anymore, but surely existed;

-------------------------------------------------------------------------------------------------------------------------------------
????????????????????????????????????????
????????????????????????????????????????
????????????????????????????????????????
???
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!

[linux-iscsi-users] where does the iscsi target save the blocks at my linux server?

[felipe g. <fe...@us...>]

I am running an iscsi target on my linux debian and I would like to know
where does it save the blocks.

Also if there is a good documentation to work with the target and edit it.

Thanks in advance! Felipe

Re: [linux-iscsi-users] Unable to attach windows guest targets running on KVM to Debian Target

[Mike C. <mic...@cs...>]

On 12/09/2011 04:14 PM, Steven Anderson wrote:
>  http://pastebin.com/G9wwwP5s <<---iscsi lunsshow up on netstat | grep
> -i 3260 as listening but I am unable to connect windows guests on KVM
> over LVM to them
> 

I think you want a different list. This list is for initiator stuff
using the linux-iscsi initaitor. It seems you are debugging the target.
I think you want the iet list.

[linux-iscsi-users] Unable to attach windows guest targets running on KVM to Debian Target

[Steven A. <hik...@ya...>]

 http://pastebin.com/G9wwwP5s <<---iscsi lunsshow up on netstat | grep -i 3260 as listening but I am unable to connect windows guests on KVM over LVM to them
help is appreciated...thanks
let me know if more information is needed

Re: [linux-iscsi-users] SN5420 linux isci

[Mike C. <mic...@cs...>]

On 09/11/2011 02:18 PM, Phil Armsdon wrote:
> 
> Hi,
>  
> Can anyone help getting a Cisco SN5420 working with Fedora 2.6.38+ kernel?  Is there a version of the open Linux iscsi driver that is compatible with both?
>  

You should use the iscsi initiator that comes with fedora.

"yum install iscsi-initiator-utils"

service iscsid start
service iscsi start

iscsiadm -m discovery -t st -p IP_ADDRESS

See /usr/share/docs/iscsi-initiator-utils-*/README


> Also, does anyone have the Cisco SN5420 v2.1.1 firmware?
>  

[linux-iscsi-users] SN5420 linux isci

[Phil A. <par...@ho...>]

Hi,
 
Can anyone help getting a Cisco SN5420 working with Fedora 2.6.38+ kernel?  Is there a version of the open Linux iscsi driver that is compatible with both?
 
Also, does anyone have the Cisco SN5420 v2.1.1 firmware?
 
Thanks,
 
Phil 		 	   		  

Re: [linux-iscsi-users] Configure iscsi.conf file for single target

[Mike C. <mic...@cs...>]

On 10/22/2010 07:16 AM, Rangel, Richard wrote:
> Thanks for the clarification on the 'TargetName'
>
> Because of specialized applications, I am stuck on Red Hat 4.5.   How do I go about using the access list?  Is that another parameter in the iscsi.conf file?
>

It is normally a feature on the target.

Re: [linux-iscsi-users] Configure iscsi.conf file for single target

[Rangel, R. <Ric...@ci...>]

Thanks for the clarification on the 'TargetName'

Because of specialized applications, I am stuck on Red Hat 4.5.   How do I go about using the access list?  Is that another parameter in the iscsi.conf file?

Richard

-----Original Message-----
From: Mike Christie [mailto:mic...@cs...] 
Sent: Thursday, October 21, 2010 3:47 PM
To: Rangel, Richard
Cc: lin...@li...
Subject: Re: [linux-iscsi-users] Configure iscsi.conf file for single target

On 10/21/2010 02:37 PM, Rangel, Richard wrote:
> I am new at this iscsi technology and thought to give it a try.
>
> Right now I am interested in trying to configure iscsi.conf file to 
> use a specific scsi target on a qnap appliance.  I thought it would be 
> as easy as using the 'DiscsveryAddress', which sees all the scsi 
> targets.  But since I want to configure for a specific target I 
> thought it would be just as easy to use the 'TargetName' with the 
> whole iqn name like so
>
> TargetName= iqn.2004-04.com.qnap:ts-809u:iscsi.flv.c08b67

The TargetName setting allows you to set settings for a specific target, or it allows you to tell iscsid to not log into specific targets returned from sendtargets discovery.

Or in RHEL 4.7 and above in iscsi.conf you can blacklist targets:

TargetName=somename
	Enabled=no

TargetName=someothername
	Enabled=no


If you only want to log into specific targets, you might want to just add the initiatorname to the target's access list. Normally, targets would then only tell the initiator about specific targets then.


The RHEL5/open-iscsi initiator allows you to specify specific target portals to log into, so you might want to try that.

Re: [linux-iscsi-users] Configure iscsi.conf file for single target

[Mike C. <mic...@cs...>]

On 10/21/2010 02:37 PM, Rangel, Richard wrote:
> I am new at this iscsi technology and thought to give it a try.
>
> Right now I am interested in trying to configure iscsi.conf file to use a specific scsi target on a qnap appliance.  I thought it would be as easy as using the 'DiscsveryAddress', which sees all the scsi targets.  But since I want to configure for a specific target I thought it would be just as easy to use the 'TargetName' with the whole iqn name like so
>
> TargetName= iqn.2004-04.com.qnap:ts-809u:iscsi.flv.c08b67

The TargetName setting allows you to set settings for a specific target, 
or it allows you to tell iscsid to not log into specific targets 
returned from sendtargets discovery.

Or in RHEL 4.7 and above in iscsi.conf you can blacklist targets:

TargetName=somename
	Enabled=no

TargetName=someothername
	Enabled=no


If you only want to log into specific targets, you might want to just 
add the initiatorname to the target's access list. Normally, targets 
would then only tell the initiator about specific targets then.


The RHEL5/open-iscsi initiator allows you to specify specific target 
portals to log into, so you might want to try that.

[linux-iscsi-users] Configure iscsi.conf file for single target

[Rangel, R. <Ric...@ci...>]

I am new at this iscsi technology and thought to give it a try.

Right now I am interested in trying to configure iscsi.conf file to use a specific scsi target on a qnap appliance.  I thought it would be as easy as using the 'DiscsveryAddress', which sees all the scsi targets.  But since I want to configure for a specific target I thought it would be just as easy to use the 'TargetName' with the whole iqn name like so

TargetName= iqn.2004-04.com.qnap:ts-809u:iscsi.flv.c08b67

After restarting the iscsi daemon I am not able to see the scsi target. The OS I am on is Red Hat E4 using the
rpm package iscsi-initiator-utils-4.0.3.0-5

Any guidance would be appreciated.

Re: [linux-iscsi-users] Max number of luns

[Mike C. <mic...@cs...>]

On 10/14/2010 06:17 AM, David Ramsay wrote:
> Hey,
>      Does linux-iscsi have a maximum number of luns that it can receive
> from a target. i.e. open-iscsi has a max of 512. is there a similar

open-iscsi's limit can be overriden with the iscsi_tcp max_lun modparam.

> limit in linux-iscsi?
>

linux-iscsi's depends on the version. The one shipped with RHEL 4 is 256.

[linux-iscsi-users] Max number of luns

[David R. <dav...@cp...>]

Hey,
    Does linux-iscsi have a maximum number of luns that it can receive
from a target. i.e. open-iscsi has a max of 512. is there a similar
limit in linux-iscsi?

-- 
David Ramsay

[SYSAdmin]

Re: [linux-iscsi-users] devicenames already taken

[Mike C. <mic...@cs...>]

On 09/22/2010 06:49 AM, Rupertt wrote:
> Hi,
>
> when I initiate my iscsi device it gets /dev/sda*, but I already have my
> swap on sda1.
>
> I followed the guide at
> http://www.idevelopment.info/data/Unix/Linux/LINUX_ConnectingToAniSCSITargetWithOpen-iSCSIInitiatorUsingLinux.shtml#iSCSI%20Technology
> and it does create some links in /dev/iscsi, but fdisk -l still shows me
> /dev/dda* for my iscsi device.
> This is very confusing and I always fear I kill my local HD Partitions.
> Is there a way to get the iscsi driver to create some unique device names
> live /dev/iscsid1 or so?
>

What distro are you using?

Most modern distros will have a /dev/disk dir and in a subdir in there 
each device will get a unique persistent name that should be used.

[linux-iscsi-users] devicenames already taken

[Rupertt <ru...@gm...>]

Hi,

when I initiate my iscsi device it gets /dev/sda*, but I already have my
swap on sda1.

I followed the guide at
http://www.idevelopment.info/data/Unix/Linux/LINUX_ConnectingToAniSCSITargetWithOpen-iSCSIInitiatorUsingLinux.shtml#iSCSI%20Technology
and it does create some links in /dev/iscsi, but fdisk -l still shows me
/dev/dda* for my iscsi device.
This is very confusing and I always fear I kill my local HD Partitions.
Is there a way to get the iscsi driver to create some unique device names
live /dev/iscsid1 or so?


greetings


.

[linux-iscsi-users] 10Gbe copper iSCSI

[Valerio A. <val...@co...>]

  Has anyone built an iSCSI SAN on 10Gbe copper and willing to share 
read/write performance numbers?

Thanks,

Valerio

[linux-iscsi-users] iscsi support AIX concurrent VG?

[penglj <pe...@ya...>]

[r3p01:/]# lspv 
hdisk0          00cc82ef582b073d                    rootvg          active 
hdisk1          00cc82efbca5658e                    rootvg          active 
hdisk3          00cc82ef4eb0aac2                    datavg         
concurrent 
hdisk4          00cc82ef50c4bf4b                    datavg         
concurrent

[r3p02:/]# lspv 
hdisk0          00cc82ef582b073d                    rootvg          active 
hdisk1          00cc82efbca5658e                    rootvg          active 
hdisk3          00cc82ef4eb0aac2                    datavg         
concurrent 
hdisk4          00cc82ef50c4bf4b                    datavg         
concurrent

error info: 

B6267342   0529164310 P H hdisk3         DISK OPERATION ERROR 
DCB47997   0529163810 T H hdisk3         DISK OPERATION ERROR 
DCB47997   0529163710 T H hdisk3         DISK OPERATION ERROR 
So I think that iscsi can't support Concurrent VG. I hope that I am wrong.
-- 
View this message in context: http://old.nabble.com/iscsi-support-AIX-concurrent-VG--tp28727026p28727026.html
Sent from the linux-iscsi-users mailing list archive at Nabble.com.

Re: [linux-iscsi-users] iSCSI persistent device naming

[bambara <m_o...@ho...>]

what i can find in /dev/disk ?????
when i reboot  i have this message : /etc/udev/scripts/iscsidev.sh failed 
i dont  understand you answar
thanks 

Mike Christie wrote:
> 
> On 04/23/2010 07:09 AM, bambara wrote:
>>
>> hello i did all what you post but it dosnt work
>> i type same code
>> i m working on redhat 5.3 and i want use udev for scsi
>> when i reboot i have this message :
>> udevd-event[11587]: run_program: exec of program
>> '/etc/udev/scripts/iscsidev' failed
> 
> iscsidev does not exist on RHEL 5.
> 
> udev should already be making names in /dev/disk/ for you. What is wrong 
> with them?
> 
>> plzz help
>> i dont know wich udev version is compatible with my redhat 5.3
>> thanks
>>
>>
>> Phani Sikharam wrote:
>>>
>>> Hi, it works fine with the below configuration on RHEL4...
>>>
>>> #cat /etc/udev/rules.d/55-iscsi.rules
>>>
>>>
>>> KERNEL="sd[a-z]*", BUS="scsi", PROGRAM="/etc/udev/scripts/iscsi.sh
>>> %b",SYMLINK="iscsi/%c/part%n"
>>>
>>>
>>>
>>> #cat /etc/udev/scripts/iscsi.sh
>>>
>>>
>>> #!/bin/sh
>>>
>>> # FILE: /etc/udev/scripts/iscsi.sh
>>>
>>> BUS=${1}
>>> HOST=${BUS%%:*}
>>>
>>> [ -e /sys/class/iscsi_host ] || exit 1
>>>
>>> #file="/sys/class/iscsi_host/host${HOST}/device/session*/iscsi_session*/targetname"
>>> file="/sys/class/iscsi_transport/target${HOST}:0:0/target_name"
>>>
>>> target_name=$(cat ${file})
>>>
>>> # This is not an open-scsi drive
>>> if [ -z "${target_name}" ]; then
>>>     exit 1
>>> fi
>>>
>>> echo "${target_name##*.}"
>>> #echo "${target_name}"
>>>
>>
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> linux-iscsi-users mailing list
> lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-iscsi-users
> 
> 

-- 
View this message in context: http://old.nabble.com/iSCSI-persistent-device-naming-tp6774978p28352612.html
Sent from the linux-iscsi-users mailing list archive at Nabble.com.

Re: [linux-iscsi-users] iSCSI persistent device naming

[Mike C. <mic...@cs...>]

On 04/23/2010 07:09 AM, bambara wrote:
>
> hello i did all what you post but it dosnt work
> i type same code
> i m working on redhat 5.3 and i want use udev for scsi
> when i reboot i have this message :
> udevd-event[11587]: run_program: exec of program
> '/etc/udev/scripts/iscsidev' failed

iscsidev does not exist on RHEL 5.

udev should already be making names in /dev/disk/ for you. What is wrong 
with them?

> plzz help
> i dont know wich udev version is compatible with my redhat 5.3
> thanks
>
>
> Phani Sikharam wrote:
>>
>> Hi, it works fine with the below configuration on RHEL4...
>>
>> #cat /etc/udev/rules.d/55-iscsi.rules
>>
>>
>> KERNEL="sd[a-z]*", BUS="scsi", PROGRAM="/etc/udev/scripts/iscsi.sh
>> %b",SYMLINK="iscsi/%c/part%n"
>>
>>
>>
>> #cat /etc/udev/scripts/iscsi.sh
>>
>>
>> #!/bin/sh
>>
>> # FILE: /etc/udev/scripts/iscsi.sh
>>
>> BUS=${1}
>> HOST=${BUS%%:*}
>>
>> [ -e /sys/class/iscsi_host ] || exit 1
>>
>> #file="/sys/class/iscsi_host/host${HOST}/device/session*/iscsi_session*/targetname"
>> file="/sys/class/iscsi_transport/target${HOST}:0:0/target_name"
>>
>> target_name=$(cat ${file})
>>
>> # This is not an open-scsi drive
>> if [ -z "${target_name}" ]; then
>>     exit 1
>> fi
>>
>> echo "${target_name##*.}"
>> #echo "${target_name}"
>>
>

Re: [linux-iscsi-users] iSCSI persistent device naming

[bambara <m_o...@ho...>]

hello i did all what you post but it dosnt work
i type same code
i m working on redhat 5.3 and i want use udev for scsi 
when i reboot i have this message :
udevd-event[11587]: run_program: exec of program
'/etc/udev/scripts/iscsidev' failed
plzz help 
i dont know wich udev version is compatible with my redhat 5.3 
thanks 


Phani Sikharam wrote:
> 
> Hi, it works fine with the below configuration on RHEL4...
> 
> #cat /etc/udev/rules.d/55-iscsi.rules
> 
> 
> KERNEL="sd[a-z]*", BUS="scsi", PROGRAM="/etc/udev/scripts/iscsi.sh
> %b",SYMLINK="iscsi/%c/part%n"
> 
> 
> 
> #cat /etc/udev/scripts/iscsi.sh
> 
> 
> #!/bin/sh
> 
> # FILE: /etc/udev/scripts/iscsi.sh
> 
> BUS=${1}
> HOST=${BUS%%:*}
> 
> [ -e /sys/class/iscsi_host ] || exit 1
> 
> #file="/sys/class/iscsi_host/host${HOST}/device/session*/iscsi_session*/targetname"
> file="/sys/class/iscsi_transport/target${HOST}:0:0/target_name"
> 
> target_name=$(cat ${file})
> 
> # This is not an open-scsi drive
> if [ -z "${target_name}" ]; then
>    exit 1
> fi
> 
> echo "${target_name##*.}"
> #echo "${target_name}" 
> 

-- 
View this message in context: http://old.nabble.com/iSCSI-persistent-device-naming-tp6774978p28340498.html
Sent from the linux-iscsi-users mailing list archive at Nabble.com.

Re: [linux-iscsi-users] iSCSI persistent device naming

[Phani S. <hu_...@ya...>]

Hi, it works fine with the below configuration on RHEL4...

#cat /etc/udev/rules.d/55-iscsi.rules


KERNEL="sd[a-z]*", BUS="scsi", PROGRAM="/etc/udev/scripts/iscsi.sh
%b",SYMLINK="iscsi/%c/part%n"



#cat /etc/udev/scripts/iscsi.sh


#!/bin/sh

# FILE: /etc/udev/scripts/iscsi.sh

BUS=${1}
HOST=${BUS%%:*}

[ -e /sys/class/iscsi_host ] || exit 1

#file="/sys/class/iscsi_host/host${HOST}/device/session*/iscsi_session*/targetname"
file="/sys/class/iscsi_transport/target${HOST}:0:0/target_name"

target_name=$(cat ${file})

# This is not an open-scsi drive
if [ -z "${target_name}" ]; then
   exit 1
fi

echo "${target_name##*.}"
#echo "${target_name}" 
-- 
View this message in context: http://old.nabble.com/iSCSI-persistent-device-naming-tp6774978p27659406.html
Sent from the linux-iscsi-users mailing list archive at Nabble.com.

[linux-iscsi-users] iSCSI for RHel ia64

[Antão C. - A. <a.c...@po...>]

Hi,
I Would like to know if u have a rpm for ia64 Red Hat EL 4.0
Thanks
AMC

[linux-iscsi-users] iSCSI SAN deployment in RHEL5.3 step by step.

[sandeep c. <sun...@re...>]

Happy new year to all !

I am a new by in Linux. I have gone through many papers on the mentioned subject but still i am not able to configure the iscsi initiator in rhel 5.3 server.The problem arises when i am asked to do the execution steps. Actually i dnt know how to do execution.

I am unable to proceed further. There are 2 Ethernet ports, 1 is used for LAN & other i have planned to configure on iscsi using Microsoft iscsi initiator.can any one help me out please...... 



regards 

Sandeep