Re: [PATCH 5/8] linux: drop __bitwise__ everywhere
t; +typedef uint32_t __bitwise itt_t; /* below makes sense only for initiator that created this tag */ #define build_itt(itt, age) ((__force itt_t)\ ((itt) | ((age) << ISCSI_AGE_SHIFT))) diff --git a/include/target/target_core_base.h b/include/target/target_core_base.h index c211900..0055828 100644 --- a/include/target/target_core_base.h +++ b/include/target/target_core_base.h @@ -149,7 +149,7 @@ enum se_cmd_flags_table { * Used by transport_send_check_condition_and_sense() * to signal which ASC/ASCQ sense payload should be built. */ -typedef unsigned __bitwise__ sense_reason_t; +typedef unsigned __bitwise sense_reason_t; enum tcm_sense_reason_table { #define R(x) (__force sense_reason_t )(x) diff --git a/include/uapi/linux/virtio_types.h b/include/uapi/linux/virtio_types.h index e845e8c..55c3b73 100644 --- a/include/uapi/linux/virtio_types.h +++ b/include/uapi/linux/virtio_types.h @@ -39,8 +39,8 @@ * - __le{16,32,64} for standard-compliant virtio devices */ -typedef __u16 __bitwise__ __virtio16; -typedef __u32 __bitwise__ __virtio32; -typedef __u64 __bitwise__ __virtio64; +typedef __u16 __bitwise __virtio16; +typedef __u32 __bitwise __virtio32; +typedef __u64 __bitwise __virtio64; #endif /* _UAPI_LINUX_VIRTIO_TYPES_H */ diff --git a/net/ieee802154/6lowpan/6lowpan_i.h b/net/ieee802154/6lowpan/6lowpan_i.h index 5ac7789..ac7c96b 100644 --- a/net/ieee802154/6lowpan/6lowpan_i.h +++ b/net/ieee802154/6lowpan/6lowpan_i.h @@ -7,7 +7,7 @@ #include #include -typedef unsigned __bitwise__ lowpan_rx_result; +typedef unsigned __bitwise lowpan_rx_result; #define RX_CONTINUE((__force lowpan_rx_result) 0u) #define RX_DROP_UNUSABLE ((__force lowpan_rx_result) 1u) #define RX_DROP((__force lowpan_rx_result) 2u) diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h index d37a577..b2069fb 100644 --- a/net/mac80211/ieee80211_i.h +++ b/net/mac80211/ieee80211_i.h @@ -159,7 +159,7 @@ enum ieee80211_bss_valid_data_flags { IEEE80211_BSS_VALID_ERP = BIT(3) }; -typedef unsigned __bitwise__ ieee80211_tx_result; +typedef unsigned __bitwise ieee80211_tx_result; #define TX_CONTINUE((__force ieee80211_tx_result) 0u) #define TX_DROP((__force ieee80211_tx_result) 1u) #define TX_QUEUED ((__force ieee80211_tx_result) 2u) @@ -180,7 +180,7 @@ struct ieee80211_tx_data { }; -typedef unsigned __bitwise__ ieee80211_rx_result; +typedef unsigned __bitwise ieee80211_rx_result; #define RX_CONTINUE((__force ieee80211_rx_result) 0u) #define RX_DROP_UNUSABLE ((__force ieee80211_rx_result) 1u) #define RX_DROP_MONITOR((__force ieee80211_rx_result) 2u) For net/ieee802154/6lowpan/6lowpan_i.h Acked-by: Stefan Schmidt regards Stefan Schmidt -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: [PATCH 17/26] mac802154: Use skcipher
Hello. On 24/01/16 14:18, Herbert Xu wrote: This patch replaces uses of blkcipher with skcipher. Signed-off-by: Herbert Xu --- net/mac802154/llsec.c | 41 +++-- net/mac802154/llsec.h |3 +-- 2 files changed, 24 insertions(+), 20 deletions(-) diff --git a/net/mac802154/llsec.c b/net/mac802154/llsec.c index a13d02b..6a3e1c2 100644 --- a/net/mac802154/llsec.c +++ b/net/mac802154/llsec.c @@ -17,9 +17,9 @@ #include #include #include -#include #include #include +#include #include "ieee802154_i.h" #include "llsec.h" @@ -144,18 +144,18 @@ llsec_key_alloc(const struct ieee802154_llsec_key *template) goto err_tfm; } - key->tfm0 = crypto_alloc_blkcipher("ctr(aes)", 0, CRYPTO_ALG_ASYNC); + key->tfm0 = crypto_alloc_skcipher("ctr(aes)", 0, CRYPTO_ALG_ASYNC); if (IS_ERR(key->tfm0)) goto err_tfm; - if (crypto_blkcipher_setkey(key->tfm0, template->key, - IEEE802154_LLSEC_KEY_SIZE)) + if (crypto_skcipher_setkey(key->tfm0, template->key, + IEEE802154_LLSEC_KEY_SIZE)) goto err_tfm0; return key; err_tfm0: - crypto_free_blkcipher(key->tfm0); + crypto_free_skcipher(key->tfm0); err_tfm: for (i = 0; i < ARRAY_SIZE(key->tfm); i++) if (key->tfm[i]) @@ -175,7 +175,7 @@ static void llsec_key_release(struct kref *ref) for (i = 0; i < ARRAY_SIZE(key->tfm); i++) crypto_free_aead(key->tfm[i]); - crypto_free_blkcipher(key->tfm0); + crypto_free_skcipher(key->tfm0); kzfree(key); } @@ -620,15 +620,17 @@ llsec_do_encrypt_unauth(struct sk_buff *skb, const struct mac802154_llsec *sec, { u8 iv[16]; struct scatterlist src; - struct blkcipher_desc req = { - .tfm = key->tfm0, - .info = iv, - .flags = 0, - }; + SKCIPHER_REQUEST_ON_STACK(req, key->tfm0); + int err; llsec_geniv(iv, sec->params.hwaddr, &hdr->sec); sg_init_one(&src, skb->data, skb->len); - return crypto_blkcipher_encrypt_iv(&req, &src, &src, skb->len); + skcipher_request_set_tfm(req, key->tfm0); + skcipher_request_set_callback(req, 0, NULL, NULL); + skcipher_request_set_crypt(req, &src, &src, skb->len, iv); + err = crypto_skcipher_encrypt(req); + skcipher_request_zero(req); + return err; } static struct crypto_aead* @@ -830,11 +832,8 @@ llsec_do_decrypt_unauth(struct sk_buff *skb, const struct mac802154_llsec *sec, unsigned char *data; int datalen; struct scatterlist src; - struct blkcipher_desc req = { - .tfm = key->tfm0, - .info = iv, - .flags = 0, - }; + SKCIPHER_REQUEST_ON_STACK(req, key->tfm0); + int err; llsec_geniv(iv, dev_addr, &hdr->sec); data = skb_mac_header(skb) + skb->mac_len; @@ -842,7 +841,13 @@ llsec_do_decrypt_unauth(struct sk_buff *skb, const struct mac802154_llsec *sec, sg_init_one(&src, data, datalen); - return crypto_blkcipher_decrypt_iv(&req, &src, &src, datalen); + skcipher_request_set_tfm(req, key->tfm0); + skcipher_request_set_callback(req, 0, NULL, NULL); + skcipher_request_set_crypt(req, &src, &src, datalen, iv); + + err = crypto_skcipher_decrypt(req); + skcipher_request_zero(req); + return err; } static int diff --git a/net/mac802154/llsec.h b/net/mac802154/llsec.h index 950578e..6f3b658 100644 --- a/net/mac802154/llsec.h +++ b/net/mac802154/llsec.h @@ -19,7 +19,6 @@ #include #include -#include #include #include #include @@ -30,7 +29,7 @@ struct mac802154_llsec_key { /* one tfm for each authsize (4/8/16) */ struct crypto_aead *tfm[3]; - struct crypto_blkcipher *tfm0; + struct crypto_skcipher *tfm0; struct kref ref; }; Reviewed-by: Stefan Schmidt regards Stefan Schmidt -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: Slow / Performance problem.
Thanks for the messages, I have change the open-iscsi settings with Citrix Perfomance settings, and i have set the blockdev to 16384, i see more perfomance. But the first dir or commando on the dir, give the same slow perfomace, it wil be taken more than 30 secondes. We not running any nis or radius server. On Tuesday, December 2, 2014 4:54:07 PM UTC+1, Juergen G wrote: > > Than you should at least tune your iscsi.conf to fit the eql > requirements. I sent a working config from one of our Systems (but keep > in mind this is multiple Gbit, not 10G). > > You can take the Manual for Citrix Xenserver Multipathing + Eql to get a > Direction how it should look like since its using open-iscsi, too. > > http://en.community.dell.com/techcenter/extras/m/white_papers/20438058 > > Dont forget to check/set the NIC Settings ... regarding the HP Switch i > am out, we where into EQL + Cisco 3750 and had lots of trouble until we > replaced them with recommended Powerconnects. > > Am 02.12.2014 um 16:43 schrieb Stefan B: > > We can not hit kit installed thats is correct, the system are not > > support get i back from the installer. > > > > We use the fowling switchs > > > > Dell Bladecenter we use the Dell PowerEdge M I/O Aggregator connect with > > 10Gbit to HP Procruve 3800 switchs and then connected to the 1Gbit > > Equallogic's. > > > > Sometime its takes more than 30 / 45 seconds to get the data back, and > > the sql and webserver are waiting on this, are the some setting whate > > can give this problem ? > > > > On Tuesday, December 2, 2014 3:22:22 PM UTC+1, Stefan B wrote: > > > > We have 2 Equallogic Systems, And a Dell Servers. > > > > We have every server give a block device home dir , so the user data > > are on the home dir this is working great its format on xfs > > filesystem, and running iscsiadm version 2.0-870 with linux kernel > > 3.10.57 > > > > But when we logging on the server, the first time we do a dir > > command on the home dir, its take a long time when we get feedback > > on the dir , the next time is fast when we do a dir. > > Now we have users on this systems and this problem give not good > > performance on sql and websites an e-mail we are running on the > server. > > > > Are the some information how i can fix ore maybe get this problem > > better under control ? > > > > I hope so that somebody can help me, i am searching for more than 3 > > weeks now. > > > > -- > > You received this message because you are subscribed to the Google > > Groups "open-iscsi" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to open-iscsi+...@googlegroups.com > > <mailto:open-iscsi+unsubscr...@googlegroups.com >. > > To post to this group, send email to open-...@googlegroups.com > > > <mailto:open-...@googlegroups.com >. > > Visit this group at http://groups.google.com/group/open-iscsi. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: Slow dir / Performance.
Thanks for the messages, I have change the open-iscsi settings with Citrix Perfomance settings, and i have set the blockdev to 16384, i see more perfomance. But the first dir or commando on the dir, give the same slow perfomace, it wil be taken more than 30 secondes. We not running any nis or radius server. On Wednesday, December 3, 2014 8:24:06 AM UTC+1, Uli wrote: > > >>> > schrieb am 02.12.2014 um 15:06 in > Nachricht > <5a7097b3-0dd7-4c28-abbf-ff66800b8...@googlegroups.com >: > > We have 2 Equallogic Systems, And a Dell Servers. > > > > We have every server give a block device home dir , so the user data are > on > > the home dir this is working great its format on xfs filesystem, and > > running iscsiadm version 2.0-870 with linux kernel 3.10.57 > > > > But when we logging on the server, the first time we do a dir command on > > the home dir, its take a long time when we get feedback on the dir , the > > next time is fast when we do a dir. > > Are you sure it's related to iSCSI? Especially for the /home dire several > different UIDs/GIDs are involved. We had a slow "ls -l /home" performance > when the NIS server had a problem. Maybe you use LDAP or something else? > Maybe try "hdparm -t " to get a rough number how fast your > block device can be read. I know there are better tests, but this one is > quick and easy to perform... > > > Now we have users on this systems and this problem give not good > > performance on sql and websites an e-mail we are running on the server. > > You are running a database ("sql") via iSCSI? > > > > > Are the some information how i can fix ore maybe get this problem better > > under control ? > > > > I hope so that somebody can help me, i am searching for more than 3 > weeks > > now. > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "open-iscsi" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to open-iscsi+...@googlegroups.com . > > To post to this group, send email to open-...@googlegroups.com > . > > Visit this group at http://groups.google.com/group/open-iscsi. > > For more options, visit https://groups.google.com/d/optout. > > > > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: Slow / Performance problem.
We can not hit kit installed thats is correct, the system are not support get i back from the installer. We use the fowling switchs Dell Bladecenter we use the Dell PowerEdge M I/O Aggregator connect with 10Gbit to HP Procruve 3800 switchs and then connected to the 1Gbit Equallogic's. Sometime its takes more than 30 / 45 seconds to get the data back, and the sql and webserver are waiting on this, are the some setting whate can give this problem ? On Tuesday, December 2, 2014 3:22:22 PM UTC+1, Stefan B wrote: > > We have 2 Equallogic Systems, And a Dell Servers. > > We have every server give a block device home dir , so the user data are > on the home dir this is working great its format on xfs filesystem, and > running iscsiadm version 2.0-870 with linux kernel 3.10.57 > > But when we logging on the server, the first time we do a dir command on > the home dir, its take a long time when we get feedback on the dir , the > next time is fast when we do a dir. > Now we have users on this systems and this problem give not good > performance on sql and websites an e-mail we are running on the server. > > Are the some information how i can fix ore maybe get this problem better > under control ? > > I hope so that somebody can help me, i am searching for more than 3 weeks > now. > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Re: Slow / Performance problem.
bash-4.3# iscsiadm -m session -P3 iSCSI Transport Class version 2.0-870 version 2.0-872 Target: iqn.2001-05.com.equallogic:0-8a0906-6c5f17a03-1244d61b0964922b-srv2 Current Portal: 192.3.168.39:3260,1 Persistent Portal: 192.3.168.25:3260,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.2005-03.org.open-iscsi:17bf658bc39 Iface IPaddress: 192.3.168.51 Iface HWaddress: default Iface Netdev: default SID: 1 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 131072 MaxXmitDataSegmentLength: 65536 FirstBurstLength: 65536 MaxBurstLength: 262144 ImmediateData: Yes InitialR2T: No MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 7State: running scsi7 Channel 00 Id 0 Lun: 0 We have not the Hit Kit installed on the Servers. We use Jumbo frames on the switches thats work, but flowcontrol dont work with the switch in the Dell Bladecenter. We use the default mount point /dev/sde on /home type xfs (rw) -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
Slow / Performance problem.
We have 2 Equallogic Systems, And a Dell Servers. We have every server give a block device home dir , so the user data are on the home dir this is working great its format on xfs filesystem, and running iscsiadm version 2.0-870 with linux kernel 3.10.57 But when we logging on the server, the first time we do a dir command on the home dir, its take a long time when we get feedback on the dir , the next time is fast when we do a dir. Now we have users on this systems and this problem give not good performance on sql and websites an e-mail we are running on the server. Are the some information how i can fix ore maybe get this problem better under control ? I hope so that somebody can help me, i am searching for more than 3 weeks now. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To post to this group, send email to open-iscsi@googlegroups.com. Visit this group at http://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
iSCSI initiator
Hi guys, i'm trying to create a new iscsi based storage system using the "new" LIO implementation. I'm just wondering which module / software should be used on client side. Until now we're using Open-iSCSI but for example on http://linux-iscsi.org/wiki/Core-iSCSI you read that Open-iSCSI is slow and old and you should use Core-iSCSI but Core-ISCSI is also at least 5 years old and doesn't even compile against an actual kernel. I'm now totally confused what the the up2date way for iSCSI under Linux is. I'm NOT ON list so please CC me. Greets Stefan -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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=en.
open-iscsi-2.0-871 on ubuntu 9.10
Hello all, Im having trouble to get open-iscsi running on ubuntu 9.10. Im thinking he *.870 is not working correctly. Cause having trouble to get it discovering. So I want to try 871. doing: /software/open-iscsi-2.0-871# ls COPYING Changelog Makefile README THANKS debian doc etc include kernel test usr utils r...@monster:~/software/open-iscsi-2.0-871# make install make -C kernel install_kernel make[1]: Entering directory `/home/stefan/software/open-iscsi-2.0-871/kernel' make[1]: *** No rule to make target `linux_2_6_31', needed by `kernel_check'. Stop. make[1]: Leaving directory `/home/stefan/software/open-iscsi-2.0-871/kernel' make: *** [install_kernel] Error 2 Can not find any information what is missing or what Im doing wrong. Can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
multiple clients same iscsi content and mount
Hello all, I want to have multiple clients with same iscsi content. Do I need then a cluster filesyststem? Should I use same "target iqn" on each client? Could not find a google entry how to do it. In the moment I have an ext3 on it. When I want to write to that device a get a read only filesystem. How to mount it read write? my fstab: /dev/sdc5 /mnt/iscsi-san ext3_netdev 0 0 What is the best way todo all these things? Can someone help? BTW. Is there a open-iscsi IRQ? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: solved compile the latest version debian ubuntu
Am Dienstag 23 Juni 2009 18:21:19 schrieb Mike Christie: ist seems that was really a kernel issue. I installed it then from repository linux image 2.6.29 and it its now working. With my own compiled kernel I did something wrong cause I used a config from an another kernel. hmm. deleting /etc/iscsi und copy from another location inistiatorname and iscsid.conf. edititing initaitorname, start Then there was a issue with login and I edit under nodes the password and I was then able to login!!! Thanks all for help stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Mittwoch 24 Juni 2009 11:47:55 schrieb Boaz Harrosh: > > This is very old what Kernel is this ? > okay I copiled new kernel: 2.6.30 uname -a Linux willy 2.6.30 #1 SMP Wed Jun 24 15:18:23 CEST 2009 i686 GNU/Linux doing: /etc/init.d/open-iscsi stop Disconnecting iSCSI targets:. Stopping iSCSI initiator service:. r...@willy:/etc/iscsi# iscsistart -i iqn.lenny.org.open-iscsi:7e84634e3e00 -t iqn.fromlenny.com.openfiler:tsn.7480be2c6f3f -g 1 -a 10.100.100.30 iscsistart: Missing or Invalid version from /sys/module/scsi_transport_iscsi/version. Make sure a up to date scsi_transport_iscsi module is loaded and a up todate version of iscsid is running. Exiting... hmm, what to do? Im trying also make user... but version dont change: /etc/iscsi# /etc/init.d/open-iscsi start Starting iSCSI initiator service: iscsid. Setting up iSCSI targets:iscsiadm: No records found! . r...@willy:/etc/iscsi# iscsiadm -m discovery -t sendtargets -p 10.100.100.30 --login dont do nothing?! iscsiadm -m session -P 3 iscsiadm: No active sessions. dmesg: 264.156290] ip_tables: (C) 2000-2006 Netfilter Core Team [ 572.562666] Loading iSCSI transport class v2.0-870. [ 573.610875] iscsi: registered transport (tcp) [ 574.880785] iscsi: registered transport (iser) and its like before: no discover possible can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Dienstag 23 Juni 2009 18:21:19 schrieb Mike Christie: > > echo - - - > /sys/class/scsi_host/hostX > > Here you can find the value of X in the iscsiadm -m session -P 3 output. > It is the Host Number value. > > So you could do > > iscsiadm -m session -P 3 | grep "Host Number" > ls /sys/class/scsi_host/ host0 r...@willy:/root# iscsiadm -m session -P 3 | grep 0 iscsiadm: could not read session targetname: 61 iscsiadm: could not find session info for session1 iscsiadm: Can not get list of active sessions (61) iSCSI Transport Class version 2.0-869 iscsiadm version 2.0-870 its now on lenny. I tried to install the latest version, it seems with no luck with: make user; sudo make install_user tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Montag 22 Juni 2009 13:51:17 schrieb Stefan: Hello all, sorry, its half solved. Its now running on ubuntu jaunty but not on debian lenny. I did what did on the ubuntu machine: aptitude install open-iscsi untar new package make user make install_user /etc/init.d/open-iscsi start iscsiadm -m session -P 3 iSCSI Transport Class version 2.0-869 iscsiadm version 2.0-870 iscsiadm: could not read session targetname: 61 iscsiadm: could not find session info for session1 iscsiadm: Can not get list of active sessions (61) And I compile x.871 but its not shown?! iscsiadm -m discovery -t sendtargets -p 10.100.100.30 --login and nothing happens then. I have look with tcpdump port 3260 on lenny and I see that nothing is recorded. Whats wrong? Can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: solved compile the latest version debian ubuntu
Am Montag 22 Juni 2009 12:05:00 schrieb Boaz Harrosh: I get now the disk. I forgott to map tghe LUNs on openfiler...aghh ;) thanks a lot for help!!! stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: iscsiadm: No records found! debian lenny
Am Sonntag 21 Juni 2009 18:23:03 schrieb Mike Christie: > > then iscsid will login into those targets you found when you did > discovery. iscsid will also then have the scsi layer do a scsi scan and > search for disks. If it finds them then you can mount and use them like > a local disk. If you are not seeing any disks then you probably have not > set something up right in openfiler. You are correct! I dont have LUNs mapped in openfiler arrgghhh !! thanks for help!!! stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Montag 22 Juni 2009 12:05:00 schrieb Boaz Harrosh: > > So it looks good now. Can you see your disks? /dev/sdX > no, I dont have a disk! Fdisk -l shows nothing, dmesg also not. only:: [ 7414.776740] iscsi: registered transport (tcp) [ 7415.067902] scsi8 : iSCSI Initiator over TCP/IP [ 7415.078623] scsi9 : iSCSI Initiator over TCP/IP [ 7415.091413] scsi10 : iSCSI Initiator over TCP/IP lsscsi [2:0:0:0]cd/dvd TSSTcorp CDRWDVD TS-H493B D300 /dev/sr0 [4:0:0:0]diskATA ST3500320NS MA07 - [4:0:1:0]diskATA ST3500320NS MA07 - [4:1:0:0]diskDell VIRTUAL DISK 1028 /dev/sda fdisk -l Disk /dev/sda: 498.9 GB, 498999492608 bytes 255 heads, 63 sectors/track, 60666 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0080 Device Boot Start End Blocks Id System /dev/sda1 * 1 31 248976 83 Linux /dev/sda2 32 60666 487050637+ 5 Extended /dev/sda5 32 60666 487050606 8e Linux LVM What can I try? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 262144 MaxXmitDataSegmentLength: 131072 FirstBurstLength: 262144 MaxBurstLength: 262144 ImmediateData: No InitialR2T: Yes MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 9 State: running Target: iqn.from10-100-100-4.com.openfiler:tsn.1391acfee1c6 Current Portal: 10.100.100.30:3260,1 Persistent Portal: 10.100.100.30:3260,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.2005-03.org.open-iscsi:49408c98fb0 Iface IPaddress: 10.100.100.10 Iface HWaddress: Iface Netdev: SID: 3 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 262144 MaxXmitDataSegmentLength: 131072 FirstBurstLength: 262144 MaxBurstLength: 262144 ImmediateData: No InitialR2T: Yes MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 10 State: running tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Montag 22 Juni 2009 10:05:25 schrieb Boaz Harrosh: > > First it seems that your Kernel did not come with the iSER module. > The best is to just disable it in the /etc/init.d/open-iscsi script. > find the line that does: "modprobe -q ib_iser" > and comment it out. You don't need it > > > hmm what next? How Can I get the scsi disk? > > But this is harmless please do again: > > []$ iscsiadm -m session -P 3 > like before, what is the output?? hmm, it seems it takes abit longer for starting: iscsiadm -m node session -P 3 iscsiadm: Invalid info level 3. Try 0 or 1. r...@monster:~# iscsiadm -m node session -P 1 Target: iqn.fromlenny.com.openfiler:tsn.7480be2c6f3f Portal: 10.100.100.30:3260,1 Iface Name: default Target: iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c Portal: 10.100.100.30:3260,1 Iface Name: default Target: iqn.from10-100-100-4.com.openfiler:tsn.1391acfee1c6 Portal: 10.100.100.30:3260,1 Iface Name: default tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Montag 22 Juni 2009 10:05:25 schrieb Boaz Harrosh: > > First it seems that your Kernel did not come with the iSER module. > The best is to just disable it in the /etc/init.d/open-iscsi script. > find the line that does: "modprobe -q ib_iser" > and comment it out. You don't need it > > > hmm what next? How Can I get the scsi disk? > > But this is harmless please do again: > > []$ iscsiadm -m session -P 3 > like before, what is the output?? iscsiadm -m session -P 3 iSCSI Transport Class version 2.0-870 version 2.0-871 iscsiadm: No active sessions. but iscsiadm -m node 10.100.100.30:3260,1 iqn.fromlenny.com.openfiler:tsn.7480be2c6f3f 10.100.100.30:3260,1 iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c 10.100.100.30:3260,1 iqn.from10-100-100-4.com.openfiler:tsn.1391acfee1c6 hmm?? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Montag 22 Juni 2009 08:59:04 schrieb Boaz Harrosh: > > I think for 2.6.28 Kernel the best is to run with built-in iscsi modules > and only compile and install the "install_user" from open-iscsi. > I reinstalled kernel and did the install_user install. This is working but I dont have a disk. fdisk -l dont show a disk. In /var/log/messages and dmesg I have: Loading iSCSI transport class v2.0-870. [140929.059791] iscsi: registered transport (tcp) [140929.117416] ib_iser: disagrees about version of symbol iscsi_conn_setup [140929.117422] ib_iser: Unknown symbol iscsi_conn_setup [140929.117569] ib_iser: disagrees about version of symbol iscsi_session_recovery_timedout [140929.117573] ib_iser: Unknown symbol iscsi_session_recovery_timedout [140929.118096] ib_iser: disagrees about version of symbol iscsi_conn_bind [140929.118100] ib_iser: Unknown symbol iscsi_conn_bind [140929.118370] ib_iser: disagrees about version of symbol iscsi_session_setup [140929.118373] ib_iser: Unknown symbol iscsi_session_setup [140929.119293] ib_iser: disagrees about version of symbol iscsi_conn_failure [140929.119296] ib_iser: Unknown symbol iscsi_conn_failure [140929.119429] ib_iser: disagrees about version of symbol iscsi_complete_pdu [140929.119432] ib_iser: Unknown symbol iscsi_complete_pdu [140929.119814] ib_iser: disagrees about version of symbol iscsi_register_transport [140929.119817] ib_iser: Unknown symbol iscsi_register_transport [140929.119991] ib_iser: disagrees about version of symbol __iscsi_get_task [140929.119994] ib_iser: Unknown symbol __iscsi_get_task [140929.120350] ib_iser: disagrees about version of symbol iscsi_set_param [140929.120355] ib_iser: Unknown symbol iscsi_set_param [140929.121178] ib_iser: disagrees about version of symbol iscsi_conn_get_param [140929.121184] ib_iser: Unknown symbol iscsi_conn_get_param [140929.121346] ib_iser: disagrees about version of symbol iscsi_suspend_tx [140929.121352] ib_iser: Unknown symbol iscsi_suspend_tx [140929.121673] ib_iser: disagrees about version of symbol iscsi_put_task [140929.121678] ib_iser: Unknown symbol iscsi_put_task [140929.121849] ib_iser: disagrees about version of symbol iscsi_conn_teardown [140929.121854] ib_iser: Unknown symbol iscsi_conn_teardown [140929.122173] ib_iser: disagrees about version of symbol iscsi_session_get_param [140929.122179] ib_iser: Unknown symbol iscsi_session_get_param [140929.122343] ib_iser: disagrees about version of symbol iscsi_conn_send_pdu [140929.122348] ib_iser: Unknown symbol iscsi_conn_send_pdu [140929.122711] ib_iser: disagrees about version of symbol iscsi_conn_start [140929.122717] ib_iser: Unknown symbol iscsi_conn_start [140929.122919] ib_iser: Unknown symbol iscsi_prep_unsolicit_data_pdu [140929.123593] ib_iser: disagrees about version of symbol iscsi_itt_to_ctask [140929.123598] ib_iser: Unknown symbol iscsi_itt_to_ctask [140929.124075] ib_iser: disagrees about version of symbol iscsi_host_alloc [140929.124079] ib_iser: Unknown symbol iscsi_host_alloc [140929.124768] ib_iser: disagrees about version of symbol iscsi_session_teardown [140929.124772] ib_iser: Unknown symbol iscsi_session_teardown [140929.124934] ib_iser: disagrees about version of symbol iscsi_unregister_transport [140929.124938] ib_iser: Unknown symbol iscsi_unregister_transport [140929.125146] ib_iser: disagrees about version of symbol iscsi_conn_stop [140929.125150] ib_iser: Unknown symbol iscsi_conn_stop [140929.414315] scsi9 : iSCSI Initiator over TCP/IP [140929.421590] scsi10 : iSCSI Initiator over TCP/IP [140929.428797] scsi11 : iSCSI Initiator over TCP/IP hmm what next? How Can I get the scsi disk? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: compile the latest version debian ubuntu
Am Montag 22 Juni 2009 00:44:50 schrieb Stefan: > Hello all :) okay doing make, make install, /etc/init.d/open-iscsi start: ~/software/open-iscsi-2.0-871-test4# /etc/init.d/open-iscsi start * Starting iSCSI initiator service iscsid [fail] * Setting up iSCSI targets Logging in to [iface: default, target: iqn.fromlenny.com.openfiler:tsn.7480be2c6f3f, portal: 10.100.100.30,3260] Logging in to [iface: default, target: iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c, portal: 10.100.100.30,3260] Logging in to [iface: default, target: iqn.from10-100-100-4.com.openfiler:tsn.1391acfee1c6, portal: 10.100.100.30,3260] iscsiadm: Could not login to [iface: default, target: iqn.fromlenny.com.openfiler:tsn.7480be2c6f3f, portal: 10.100.100.30,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not login to [iface: default, target: iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c, portal: 10.100.100.30,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not login to [iface: default, target: iqn.from10-100-100-4.com.openfiler:tsn.1391acfee1c6, portal: 10.100.100.30,3260]: iscsiadm: initiator reported error (12 - iSCSI driver not found. Please make sure it is loaded, and retry the operation) iscsiadm: Could not log into all portals. Err 12. modprobe iscsi_tcp WARNING: All config files need .conf: /etc/modprobe.d/vmxnet, it will be ignored in a future release. FATAL: Error inserting iscsi_tcp (/lib/modules/2.6.28-13- server/kernel/drivers/scsi/iscsi_tcp.ko): Unknown symbol in module, or unknown parameter (see dmesg) Whats wrong? can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
compile the latest version debian ubuntu
Hello all :) I want to compile the latest version and have no luck with that on debian lenny and ubuntu jaunty. Doing make install gives: ... sr/transport.h:37: error: field 'list' has incomplete type usr/transport.h:41: error: field 'sessions' has incomplete type In file included from usr/iscsi_sysfs.h:22, from usr/iscsid.c:43: usr/sysfs.h:33: error: field 'node' has incomplete type In file included from usr/iscsid.c:45: usr/session_info.h:13: error: field 'list' has incomplete type usr/iscsid.c:46:21: error: sysdeps.h: No such file or directory usr/iscsid.c: In function 'sync_session': usr/iscsid.c:198: error: 'CAP_FW_DB' undeclared (first use in this function) usr/iscsid.c:198: error: (Each undeclared identifier is reported only once usr/iscsid.c:198: error: for each function it appears in.) make: *** [usr/iscsid] Error 1 Kernel Linux monster 2.6.28-13-server #44-Ubuntu SMP Tue Jun 2 08:40:28 UTC 2009 x86_64 GNU/Linux What Im doing wrong? The readmes seems to be outdated. Is there anywhere an actually readme/ howto for compiling it? Can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: no disk after connect debian lenny ubuntu
Am Sonntag 21 Juni 2009 19:03:35 schrieb Mike Christie: > > What does that mean? Its on lenny > > You need to update your iscsi tools or move to a older kernel. Do you know which kernel I have to use? > > The kernel sysfs layout changed on us. Older tools assumed some dirs or > symlinks would be there. They got moved or deleted and so the error > messages above are from that. okay., how to use a new kernel? Is that possible? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: no disk after connect debian lenny ubuntu
Am Sonntag 21 Juni 2009 18:24:49 schrieb Mike Christie: > > If you do > > iscsiadm -m session -P 3 > iscsiadm -m session -P 3 iSCSI Transport Class version 1.1-646 iscsiadm version 2.0-870 iscsiadm: could not read session targetname: 61 iscsiadm: could not find session info for session0 iscsiadm: Can not get list of active sessions (61) What does that mean? Its on lenny on ubuntu 9.04 server I get:: iscsiadm -m session -P 3 iSCSI Transport Class version 2.0-870 iscsiadm version 2.0-870 Target: iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c Current Portal: 10.100.100.30:3260,1 Persistent Portal: 10.100.100.30:3260,1 ** Interface: ** Iface Name: default Iface Transport: tcp Iface Initiatorname: iqn.1993-08.org.debian:01:58409fc50e Iface IPaddress: 10.100.100.10 Iface HWaddress: default Iface Netdev: default SID: 1 iSCSI Connection State: LOGGED IN iSCSI Session State: LOGGED_IN Internal iscsid Session State: NO CHANGE Negotiated iSCSI params: HeaderDigest: None DataDigest: None MaxRecvDataSegmentLength: 131072 MaxXmitDataSegmentLength: 131072 FirstBurstLength: 262144 MaxBurstLength: 262144 ImmediateData: No InitialR2T: Yes MaxOutstandingR2T: 1 Attached SCSI devices: Host Number: 5 State: running r...@monster:~# iSCSI Transport Class version 1.1-646 bash: iSCSI: command not found r...@monster:~# iscsiadm version 2.0-870 iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [-R | -u | -s ] [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -k priority r...@monster:~# iscsiadm: could not read session targetname: 61 bash: iscsiadm:: command not found r...@monster:~# iscsiadm: could not find session info for session0 bash: iscsiadm:: command not found r...@monster:~# iscsiadm: Can not get list of active sessions (61) bash: syntax error near unexpected token `(' r...@monster:~# What to do? Itia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
no disk after connect debian lenny ubuntu
Hello all, I have a openfiler san and want to connect from debian lenny and ubuntu jaunty server. I have succesfull connect but dont get a disk. fdisk -l dont show the disk. Also I had a look to dmesg and messages but nothing to find. How can I get the disk ? Where to look? Afaik it should be there after doing iscsi restart but it isnt. Can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: iscsiadm: No records found! debian lenny
Am Samstag 20 Juni 2009 12:53:45 schrieb Stefan: okay, have it: I copied the configs from another machine and did a iscsi restart doing discover: iscsiadm -m discovery -t st -p 10.100.100.30 10.100.100.30:3260,1 iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c 10.100.100.30:3260,1 iqn.from10-100-100-4.com.openfiler:tsn.1391acfee1c6 10.100.100.30:3260,1 iqn.fromlenny.com.openfiler:tsn.7480be2c6f3f dont know, what was wrong with the old config but nothing is mounted and I can not find a log entry . How can I mount the scsi device now? fdisk -l shows no such scsi device. can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: iscsiadm: No records found! debian lenny
Hello, Am Donnerstag 18 Juni 2009 18:32:51 schrieb Mike Christie: > It looks like no tagrets were found. I think you might have to set > something in openfiler to allow the initiator to be able to discover > targets. Yes, I allowed 0.0.0.0/0 for accessing openfiler and there is a "incoming user" set > If targets are found then when you run that iscsiadm command something > like this: > > # iscsiadm -m discovery -t st -p 10.15.85.19:3260 > 10.15.84.19:3260,2 iqn.1992-08.com.netapp:sn.33615311 > 10.15.85.19:3260,3 iqn.1992-08.com.netapp:sn.33615311 > iscsiadm -m discovery -t st -p 10.100.100.30:3260 iscsiadm: Login failed to authenticate with target iscsiadm: discovery login to 10.100.100.30 rejected: initiator error (02/01), non-retryable, giving up iscsiadm -m discovery -t st -p 10.100.100.30:3260 --login iscsiadm: Login failed to authenticate with target iscsiadm: discovery login to 10.100.100.30 rejected: initiator error (02/01), non-retryable, giving up What to do? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: iscsiadm: No records found! debian lenny
Hello, Am Donnerstag 18 Juni 2009 17:51:04 schrieb mala...@us.ibm.com: > > What does 'iscsiadm -mode node -l' do? Does it login to the portal? iscsiadm -mode node -l iscsiadm -m discovery [ -hV ] [ -d debug_level ] [-P printlevel] [ -t type -p ip:port -I ifaceN ... [ -l ] ] | [ -p ip:port ] [ -o operation ] [ -n name ] [ -v value ] iscsiadm -m node [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -L all,manual,automatic ] [ -U all,manual,automatic ] [ -S ] [ [ -T targetname -p ip:port -I ifaceN ] [ -l | -u | -R | -s] ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m session [ -hV ] [ -d debug_level ] [ -P printlevel] [ -r sessionid | sysfsdir [ -R | -u | -s ] [ -o operation ] [ -n name ] [ -vvalue ] ] iscsiadm -m iface [ -hV ] [ -d debug_level ] [ -P printlevel ] [ -I ifacename ] [ [ -o operation ] [ -n name ] [ -v value ] ] iscsiadm -m fw [ -l ] iscsiadm -k priority doing from beginning: iscsiadm -m iface -I iface0 --op=new New interface iface0 added r...@willy:/etc/iscsi# iscsiadm -m discovery -t st -p 10.100.100.30:3260 -I iface0 -P 1 iscsiadm: Login failed to authenticate with target iscsiadm: discovery login to 10.100.100.30 rejected: initiator error (02/01), non-retryable, giving up r...@willy:/etc/iscsi# iscsiadm --mode node --targetname iqn.2006-01.com.openfiler:tsn.e1ed9b1eb42c --portal 10.100.100.30:3260 --login iscsiadm: no records found! what else can I try? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
iscsiadm: No records found! debian lenny
Hello al, I want to do a iscsi connection from a debian lenny machine do a san (openfiler.com) and getting such error when trying: iscsiadm: No records found! Im doing: iscsiadm --mode discovery --type sendtargets --portal 10.100.100.30 10.100.100.30:3260,1 iqn.2006-01.com.openfiler:tsn.c0aa34c0adda /etc/init.d/open-iscsi restart Disconnecting iSCSI targets:. Stopping iSCSI initiator service:. Starting iSCSI initiator service: iscsid. Setting up iSCSI targets: iscsiadm: No records found! nmap shows the port open from lenny machine. Can not find a log. can someone help? tia stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@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 -~--~~~~--~~--~--~---
Re: Extremely slow read performance, but write speeds are near-perfect!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A. Eijkhoudt schreef: > On Sep 12, 3:49 pm, Konrad Rzeszutek <[EMAIL PROTECTED]> wrote: >> Can you try to copy the file from the iSCSI target to /dev/null? > > Yes, no difference. It's still going at a decidedly unimpressive 1.5MB/ > sec. So what about a windows client? How fast is it going? Stefan -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjKgt0ACgkQYH1+F2Rqwn3tqwCeMD+H1u1+dqHQryH2rvAjsMee nmYAn3OUBXbGjvNeewlQCJdG2eceEpUx =ISaT -END PGP SIGNATURE- --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Reducing amount of logmessages openiscsi/multipath
Kees Hoekzema schreef: > So my questions: > - Is there a way to suppress those messages, either in the iscsi programs or > in multipath? Filter it in your syslog daemon? > - If that fails, is it possible to tweak multipath in such a way that it > doesn't check the two failed paths, unless there is no other path available? > These two paths should become available only if the main controller dies. Did you test the last? Do they actually come up when you pull the plug on the other two cables? (Do you see the end_request for sda/sdb in that situation) Alternatively I think hacking the daemon to suppress would be trivial, but I presume any advanced syslog daemon can do the same. I wonder if it is the multipath daemon that produces the end_requests, and not something like udev/hal. But you are a Tweaker, you must be able to verify that ;) Yours Sincerely, Stefan de Konink --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Why is OpenISCSI prefering an non reachable subnet over a reachable one?
As subject. If there is any way to limit/filter the subnets sendtargets gives out I'm happy configure this. Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Maximum LUN support
On Thu, 15 May 2008, Shrey wrote: > On May 15, 12:39 pm, Stefan de Konink <[EMAIL PROTECTED]> wrote: > > On Wed, 14 May 2008, Shrey wrote: > > > I started using/studying open-iscsi recently. I was wondering if there > > > is any hard-coded limit to number of targets devices that can > > > discovered per iSCSI target? Is there any hard-coded limit on the > > > number of LUNs supported per target device (assuming that somehow HBA > > > on iscsi target doesn't present any limit) ? > > > > It is a module parameter, check modinfo. > > Thanks :) - > defined as > -module_param_named(max_lun, iscsi_max_lun, uint, S_IRUGO); > - > and has a default value of 512. > > But is there any limit on the number of target devices that can be > discovered per iscsi target? Something like "only x targets can be > fetched using sendtarget from machine B to Machine A, each having > max_lun maximum number of LUNs" > > Thanks again for the information/help. Mmm... I wanted to know this last week. And in the SCSI module there is written you can go up to 16k. But I suggest if you go above 4k to review the time that is needed to rescan ;) I don't know about targets, I only checked for luns :) Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Suggestion: creating a shared library
On Wed, 14 May 2008, Mike Christie wrote: > Are you going to make it? If so search through the list for others that > were working on it so you can work together. I have got busy with other > sutff so I have not been able to finish it. Hopefully after the offload > card support is done I can get back to it if no one else is working on it. It is trivial, I'll post an update for the Makefile. Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: Maximum LUN support
On Wed, 14 May 2008, Shrey wrote: > I started using/studying open-iscsi recently. I was wondering if there > is any hard-coded limit to number of targets devices that can > discovered per iSCSI target? Is there any hard-coded limit on the > number of LUNs supported per target device (assuming that somehow HBA > on iscsi target doesn't present any limit) ? It is a module parameter, check modinfo. Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Suggestion: creating a shared library
Hi, In the libvirt project we have stumbled upon a problem related to name changes of sys-fs. Looking at the Makefiles of open-iscsi and its usertools, I wonder if we can make it more easy for other projects using open-iscsi. I propose to move the shared sourcecode of ISCSI_LIB_SRCS into a new shared object. Something like libopen-iscsi.so, in this way other projects can have consistent functions for example get_blockdev_from_lun. Is this an option? Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
target*/*/block:change
What was the reason for adding the block device name to the block symlink if this symlink already provides this name? It probably breaks everything that uses this block path directly to find out the device it is pointing to. Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Re: iscsi root on Gentoo
On Thu, 8 May 2008, aspasia wrote: > Just wanted to find out if anyone has successfully booted a diskless > server over iscsi on a Gentoo distro? If so, did you follow a How2, > and if you don't mind to share the link? But don't you think everything is virtually the same :) I mean, what happens: kernel boots, your tiny init starts iscsid creates a disk, you switch root and start init again. Hardly magic? And is indeed for every distro the same. Now the interesting part is that there was a busybox patch for iscsi in busybox. Now if you can get that to work, you can make your own ultra tiny initrd (which ofcourse you share with the rest of us!) that takes as kernel-argument something like iscsi-rootdev=... and switches after success or retries/reboot upon failure. Maybe this tiny busybox initrd already exist, but I would consider this a nice little project :) Stefan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---
Feature Request: dynamically update max_lun
Unlike the scsi module paramater max_luns, iscsi's max_lun cannot be set on the fly. It requires unloading the module and loading it again. Would it be possible to add the functionality? Yours Sincerely, Stefan de Konink --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to open-iscsi@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/open-iscsi -~--~~~~--~~--~--~---