Re: iSCSI SAN on copper 10Gbe
Valerio wrote: Has anyone built an iSCSI SAN on 10Gbe copper and willing to share read/write performance numbers? This (performance) is dependent upon many things. Back end storage, size/distribution of reads/writes, etc. Do you have particular workloads you are interested in? Or just raw bulk streaming storage? -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
Re: iscsi performance via 10 Gig
Boaz Harrosh wrote: We reimaged the server to OpenSuse, same hardware and configs otherwise, and since then we are getting about half, or 1.2 to 1.3 Gbit per NIC, or 2.5 to 3.0 Gbit total IO throughput, but we've not had any iscsi connection errors. What are other people seeing? Doesn't need to be an equallogic, just any 10 Gig connection to an iscsi array and single host throughput numbers. ISCSI-SCST/open-iscsi on a decent hardware can fully saturate 10GbE link. On writes even with a single stream, i.e. something like a single dd writing data to a single device. Off topic question: That's a fast disk. A sata HD? the best I got for single sata was like 90 MB/s. Did you mean a RAM device of sorts. [not a commercial, just a "thumbs up"* for iSCSI-SCST] We measure (sustained) typically 500+ MB/s for our iSCSI over 10GbE using SCST for simple copies, IOMeter type loads, etc. When we push things a bit, we can (and do) saturate the link. Our back-end arrays sustain 1.8+ GB/s reads and 1.4+ GB/s writes for files much larger than RAM. Thanks Boaz Joe * "thumbs up" is a colloquialism for a recommendation. -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
Re: iSCSI target recommendation
Pasi Kärkkäinen wrote: On Sun, Mar 28, 2010 at 08:52:42AM -0400, Joe Landman wrote: An Oneironaut wrote: Hey all. Could anyone suggest a good NAS that has about 2 to 6TB of storage which is under 4k? its hard to find out whether these people have tested with open-iscsi or not. So I was hoping some of you out there who had used a storage device within this range would have some opinions. Please tell me if you have any suggestions. If you don't mind a vendor reply, have a look at http://scalableinformatics.com/deltav Not meant as a commercial, so skip/delete if you object to commercial content. And blame/flame me offline if you do object vociferously. Don't worry, the URL didn't work ;) heh ... our redirection bit died. Will fix, thanks. (It is canonically http://scalableinformatics.com/delta-v but people kept omitting the "-"). fixed, works now. -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
Re: iSCSI target recommendation
An Oneironaut wrote: Hey all. Could anyone suggest a good NAS that has about 2 to 6TB of storage which is under 4k? its hard to find out whether these people have tested with open-iscsi or not. So I was hoping some of you out there who had used a storage device within this range would have some opinions. Please tell me if you have any suggestions. If you don't mind a vendor reply, have a look at http://scalableinformatics.com/deltav Not meant as a commercial, so skip/delete if you object to commercial content. And blame/flame me offline if you do object vociferously. All units are tested/functional with open-iscsi initiator, ietd and scst targets. Linux OS based, providing simultaneous NAS (file targets: NFS, CIFS/SMB, ...), SAN (block: iSCSI targets/inititors, SRP, ...) over default transports of Gigabit, with 10GbE and Infiniband optional. We get very good performance over GbE using open-iscsi initiator to these devices, and also excellent performance running these with the open-iscsi initiator, connecting to other targets, able to saturate the multiple GbE NICs without pain. We don't list pricing for lower end units, but they would meet your pricing target. Thanks, JD -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
Re: Over one million IOPS using software iSCSI and 10 Gbit Ethernet
Bart Van Assche wrote: "1,030,000 IOPS over a single 10 Gb Ethernet link" This is less than 1us per IOP. Interesting. Their hardware may not actually support this. 10GbE typically is 7-10us, though ConnectX and some others get down to 2ish. Which I/O depth has been used in the test ? Latency matters most with an I/O depth of one and is almost irrelevant for high I/O depth values. Yes, but then they are measuring the efficiency of their caching/queuing, and not of actual physical IOPs. For one of our storage clusters at a customer site, we have demonstrated really fast writes into cache across 8000+ simultaneous writers. Its just that this number is ... well ... meaningless. Bart. -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
Re: Over one million IOPS using software iSCSI and 10 Gbit Ethernet
Pasi Kärkkäinen wrote: I think SFP+ 10 Gbit has 0.6usec latency.. ? 10GBase-T is 2.6 usec. http://www.mellanox.com/pdf/whitepapers/wp_mellanox_en_Arista.pdf They are reporting 7+ us latency. ConnectX are a bit better on latency than the Intel NICs. http://www.ednasia.com/article-24923-solarflarearistanetworkspublishtestreportdemonstratinglowlatencywith10gbe-Asia.html shows latency, server to server of ~5us. This is about what you expect (and why 10GbE isn't quite to IB capability yet in low latency apps). I suspect that they really aren't seeing ~1us latencies, but that with some neat tricks, it appears to be this. Physically, it isn't there. I'd classify this as a "marketing number" (e.g. unachievable in applications that matter). I'd be happy to be proven wrong, but there really isn't much to suggest that I am wrong. -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
Re: Over one million IOPS using software iSCSI and 10 Gbit Ethernet
Pasi Kärkkäinen wrote: Hello list, Please check these news items: http://blog.fosketts.net/2010/01/14/microsoft-intel-push-million-iscsi-iops/ http://communities.intel.com/community/openportit/server/blog/2010/01/19/100-iops-with-iscsi--thats-not-a-typo http://www.infostor.com/index/blogs_new/dave_simpson_storage/blogs/infostor/dave_simpon_storage/post987_37501094375591341.html "1,030,000 IOPS over a single 10 Gb Ethernet link" This is less than 1us per IOP. Interesting. Their hardware may not actually support this. 10GbE typically is 7-10us, though ConnectX and some others get down to 2ish. "Specifically, Intel and Microsoft clocked 1,030,000 IOPS (with 512-byte blocks), and more than 2,250MBps with large block sizes (16KB to 256KB) using the Iometer benchmark" So.. who wants to beat that using Linux + open-iscsi? :) -- Pasi -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics, Inc. email: land...@scalableinformatics.com web : http://scalableinformatics.com http://scalableinformatics.com/jackrabbit phone: +1 734 786 8423 x121 fax : +1 866 888 3112 cell : +1 734 612 4615 -- 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=en.
problem with kernel 2.6.28 but not with 2.6.27
Hi folks:
We are having a problem with kernel 2.6.28 and the git repository
code (the latest semi-stable code doesn't support 2.6.28). Same
hardware, same targets, the 2.6.27 kernel can see our targets, but
2.6.28.4 can't. RHEL 5.3 on one machine Centos 5.2 on another, both
x86_64, with git code from repository (needed due to lack of 2.6.28
support in the 870.3 code from what I could see).
Here is what we see
[r...@jackrabbit open-iscsi]# uname -r
2.6.27.5
[r...@jackrabbit open-iscsi]# iscsiadm --mode discovery --type
sendtargets --portal 192.168.5.117
192.168.5.117:3260,1 iqn.2008-08.com.scalableinformatics:tiburon.dos.boot.image
192.168.5.117:3260,1
iqn.2008-08.com.scalableinformatics:tiburon.seagate.flash.cd
192.168.5.117:3260,1
iqn.2008-08.com.scalableinformatics:tiburon.suse10.3.x64.install.dvd
192.168.5.117:3260,1
iqn.2008-08.com.scalableinformatics:tiburon.ubuntu.install.cd
192.168.5.117:3260,1 iqn.2008-10.com.scalableinformatics:tiburon.iscsi.boot.disk
but 2.6.28.4 doesn't
[r...@jackrabbit open-iscsi]# uname -r
2.6.28.4
[r...@jackrabbit open-iscsi]# iscsiadm --mode discovery --type
sendtargets --portal 192.168.5.117
iscsiadm: Cannot perform discovery. Initiatorname required.
iscsiadm: Discovery process to 192.168.5.117:3260 failed to create a
discovery session.
moreover, performing an explicit restart
/etc/init.d/open-iscsi restart
yields this:
[r...@jackrabbit ~]# /etc/init.d/open-iscsi restart
Stopping iSCSI initiator service: [ OK ]
Starting iSCSI initiator service: FATAL: Error inserting iscsi_tcp
(/lib/modules/2.6.28.4/kernel/drivers/scsi/iscsi_tcp.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting ib_iser
(/lib/modules/2.6.28.4/kernel/drivers/infiniband/ulp/iser/ib_iser.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
[ OK ]
Setting up iSCSI targets: Logging in to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.ubuntu.install.cd, portal:
192.168.5.117,3260]
Logging in to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.dos.boot.image, portal:
192.168.5.117,3260]
Logging in to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.suse10.3.x64.install.dvd,
portal: 192.168.5.117,3260]
Logging in to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.seagate.flash.cd, portal:
192.168.5.117,3260]
Logging in to [iface: default, target:
iqn.2008-10.com.scalableinformatics:tiburon.iscsi.boot.disk, portal:
192.168.5.117,3260]
iscsiadm: Could not login to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.ubuntu.install.cd, portal:
192.168.5.117,3260]:
iscsiadm: initiator reported error (13 - daemon access denied)
iscsiadm: Could not login to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.dos.boot.image, portal:
192.168.5.117,3260]:
iscsiadm: initiator reported error (13 - daemon access denied)
iscsiadm: Could not login to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.suse10.3.x64.install.dvd,
portal: 192.168.5.117,3260]:
iscsiadm: initiator reported error (13 - daemon access denied)
iscsiadm: Could not login to [iface: default, target:
iqn.2008-08.com.scalableinformatics:tiburon.seagate.flash.cd, portal:
192.168.5.117,3260]:
iscsiadm: initiator reported error (13 - daemon access denied)
iscsiadm: Could not login to [iface: default, target:
iqn.2008-10.com.scalableinformatics:tiburon.iscsi.boot.disk, portal:
192.168.5.117,3260]:
iscsiadm: initiator reported error (13 - daemon access denied)
iscsiadm: Could not log into all portals. Err 13.
In the logs, I found this:
Mar 11 01:29:25 jackrabbit iscsid: peeruser_unix: unknown local user with uid 0
I traced this with some googling to the usr/mgmt_ipc.c code. The
specific code which is tossing this error is
pass = getpwuid(peercred.uid);
if (pass == NULL) {
log_error("peeruser_unix: unknown local user with uid %d",
(int) peercred.uid);
return 0;
}
Basically the code is dying on the return from the getpwuid call.
Somehow pass is set to null for peercred.uid == 0. Strange.
As a sanity check, I compiled and built this:
#include
#include
#include
main() {
struct passwd *p;
uid_t uid=0;
if ((p = getpwuid(uid)) == NULL)
perror("getpwuid() error");
else {
printf("getpwuid() returned the following info for uid %d:\n",
(int) uid);
printf(" pw_name : %s\n", p->pw_name);
printf(" pw_uid : %d\n", (int) p->pw_uid);
printf(" pw_gid : %d\n", (int) p->pw_gid);
printf(" pw_dir : %s\n", p->pw_dir);
printf(" pw_shell : %s\n", p->pw_shell);
}
}
compiling and running the code ...
[r...@jackrabbit ~]# gcc t.c -o t.x
[r...@jackrabbit ~]# ./t.x
getpwuid() returned the following info for uid 0:
pw_name : root
pw_uid
Update (Re: open iSCSI over iSER target RPM ...)
Update: [EMAIL PROTECTED] etc]# dd if=/dev/zero of=/big/local.file bs=256k count=10 10+0 records in 10+0 records out 2621440 bytes (26 GB) copied, 58.7484 seconds, 446 MB/s Better. I rebuilt OFED 1.2.5.5. Are there specific recommended tuning guides for iSER? Backing store in this case are real disks, and we can sink/source >750 MB/s on them, so I am not worried about disk IO bottlenecks, more worried about bad config of iSCSI/iSER. BTW: the 2TB LUN limit I asked about is still here in this code. Same machines (initiator and target) used for SRP reported correct LUN sizes. Here we are using the -868 open-iscsi initiator, and the tgt RPM announced. I would like to dig into this. This is what I am getting in dmesg for this iSER target: iscsi: registered transport (tcp) iscsi: registered transport (iser) iser: iser_connect:connecting to: 10.2.1.2, port 0xbc0c iser: iser_cma_handler:event 0 conn 81024b9f69c0 id 810209748c00 iser: iser_cma_handler:event 2 conn 81024b9f69c0 id 810209748c00 iser: iser_create_ib_conn_res:setting conn 81024b9f69c0 cma_id 810209748c00: fmr_pool 81024bfb32c0 qp 8101cb16d600 iser: iser_cma_handler:event 9 conn 81024b9f69c0 id 810209748c00 iser: iscsi_iser_ep_poll:ib conn 81024b9f69c0 rc = 1 scsi13 : iSCSI Initiator over iSER, v.0.1 iser: iscsi_iser_conn_bind:binding iscsi conn 81021b65fa90 to iser_conn 81024b9f69c0 Vendor: IET Model: ControllerRev: 0001 Type: RAID ANSI SCSI revision: 05 scsi 13:0:0:0: Attached scsi generic sg2 type 12 Vendor: IET Model: VIRTUAL-DISK Rev: 0001 Type: Direct-Access ANSI SCSI revision: 05 sdc : very big device. try to use READ CAPACITY(16). sdc : READ CAPACITY(16) failed. sdc : status=1, message=00, host=0, driver=08 sdc : use 0x as device size SCSI device sdc: 4294967296 512-byte hdwr sectors (2199023 MB) sdc: Write Protect is off sdc: Mode Sense: 79 00 00 08 SCSI device sdc: drive cache: write back sdc : very big device. try to use READ CAPACITY(16). sdc : READ CAPACITY(16) failed. sdc : status=1, message=00, host=0, driver=08 sdc : use 0x as device size SCSI device sdc: 4294967296 512-byte hdwr sectors (2199023 MB) sdc: Write Protect is off sdc: Mode Sense: 79 00 00 08 SCSI device sdc: drive cache: write back sdc: unknown partition table sd 13:0:0:1: Attached scsi disk sdc sd 13:0:0:1: Attached scsi generic sg3 type 0 and this is what we get in SRP scsi6 : SRP.T10:0008F104039862A4 Vendor: SCST_BIO Model: vdisk0Rev: 096 Type: Direct-Access ANSI SCSI revision: 04 sdc : very big device. try to use READ CAPACITY(16). SCSI device sdc: 12693355130 512-byte hdwr sectors (6498998 MB) sdc: Write Protect is off sdc: Mode Sense: 6b 00 10 08 SCSI device sdc: drive cache: write back w/ FUA This looks suspiciously like a 2^32 limit somewhere. Our exported device is [EMAIL PROTECTED] ~]# parted /dev/sdb print Model: Areca jrvs1 (scsi) Disk /dev/sdb: 6500GB Sector size (logical/physical): 512B/512B Partition Table: loop Number Start End SizeFile system Flags 1 0.00kB 6500GB 6500GB xfs and this is what tgtadm reports [EMAIL PROTECTED] ~]# tgtadm --lld iscsi --op show --mode target Target 1: iqn.2001-04.com.jr1-jackrabbit.small System information: Driver: iscsi Status: running I_T nexus information: I_T nexus: 4 Initiator: iqn.1996-04.voltaire.com:01:dfaa3fd Connection: 0 RDMA IP Address: 10.2.1.1 LUN information: LUN: 0 Type: controller SCSI ID: deadbeaf1:0 SCSI SN: beaf10 Size: 0 Online: No Poweron/Reset: Yes Removable media: No Backing store: No backing store LUN: 1 Type: disk SCSI ID: deadbeaf1:1 SCSI SN: beaf11 Size: 5T Online: Yes Poweron/Reset: No Removable media: No Backing store: /dev/sdb Account information: ACL information: 10.2.1.1 So it looks like the LUN 1 is approximately correct (5T ???) on the target, and incorrect when the initiator asks for it. Please note that I have successfully used the full 6+TB as an iSCSI target using the SCST-iscsi code, so I do know that the initiator works correctly. Is there a source RPM/tree for this target? Joe Landman wrote: > Hi Erez > > Erez Zilber wrote: >> stgt (SCSI target) is an open-source framework for storage target >> drivers. It supports iSCSI over iSER among other storage target drivers. >> >> Voltaire added a git tree for stgt that will be added to OFED 1.4: >> http://www2.openfabrics.org/git/?p=~dorons/tgt.git;a=summary >> >> Until OFED 1.4 ge
Re: [ofa-general] [ANNOUNCE] open iSCSI over iSER target RPM is available
Hi Erez Erez Zilber wrote: > stgt (SCSI target) is an open-source framework for storage target > drivers. It supports iSCSI over iSER among other storage target drivers. > > Voltaire added a git tree for stgt that will be added to OFED 1.4: > http://www2.openfabrics.org/git/?p=~dorons/tgt.git;a=summary > > Until OFED 1.4 gets released, it is possible to install the stgt RPM on > top of OFED 1.3. For more details about how to install and use stgt, > please refer to https://wiki.openfabrics.org/tiki-index.php?page=ISER-target > > Some performance numbers that were measured by OSC (using SDR cards): Is there a 2TB limit on this target? It turns our 6TB partition into a 2TB lun. > * READ: 920 MB/sec > * WRITE: 850 MB/sec Not getting anything even remotely close to this. Are there more details on configuration somewhere? I followed the web page as indicated. Joe > > We hope to have DDR measurements numbers soon. > -- Joseph Landman, Ph.D Founder and CEO Scalable Informatics LLC, email: [EMAIL PROTECTED] web : http://www.scalableinformatics.com http://jackrabbit.scalableinformatics.com phone: +1 734 786 8423 fax : +1 866 888 3112 cell : +1 734 612 4615 --~--~-~--~~~---~--~~ 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: kernel panic on open-iscsi login to target
On Feb 17, 4:57 pm, Joe Landman <[EMAIL PROTECTED]> wrote: [...] > For the Centos load, this was the 5.1 kernel driver with the 865 user > space tools. "fixed" I completely rebuilt/re-installed the 865 tools after removing every trace of the previous builds (userspace and kernel modules) and rebooting. Now logins are fine without the crash. Thanks for point me in the right direction. Joe --~--~-~--~~~---~--~~ 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: kernel panic on open-iscsi login to target
Hi Mike On Feb 17, 3:52 pm, Mike Christie <[EMAIL PROTECTED]> wrote: > Joe Landman wrote: > > Hi folks: > > > I have a Ubuntu 7.10 machine with a 10 GbE card connected to a > > What target? Is this the open solaris one? SCST-iSCSI in a 2.6.23.14 kernel. > > > target. Same machine running Centos 5.1 connects with no problem to > > target using 865 code. Booting this machine into Ubuntu (2.6.22-14 > > Do mean you are using the Centos 5.1 kernel driver with the userspace > tools from 865? Or are you using the userapce and kernel modules from 865? For the Centos load, this was the 5.1 kernel driver with the 865 user space tools. I didn't build the 868 for it, but could if needed. > > > kernel by default, though we have also verified that this fails in the > > same way with a 2.6.23.14 kernel), and then attempting to log in to > > the same target that just worked with the Centos load (on that same > > machine), results in an immediate hard kernel lock. No data to screen/ > > nothing in the logs. Keyboard lights are flashing, but no real data > > as to what is the cause is available. > > > Any thoughts? Any work arounds? I have tried the 865, the 868 > > code. Thanks. > > Are you using 865/868 kernel modules and userspace tools or just the > usersapce tools with the iscsi modules from the 2.6.22-14 and 2.6.23.14 > kernels? For the Ubuntu initiator, I tried 865 tools and 865 modules, 868 tools and 868 modules. Both combinations can do discovery, but as soon as we try a login, we get a hard crash (no panic information). Initiator box is hard locked, with flashing keyboard LEDs. I built 868 with additional debugging, and this didn't help (to get error messages out). I can try different kernels, but I observed this with 2.6.22-14 (baseline Ubuntu 7.10 load) as well as our special built 2.6.23.14. We are using Trond's 2.6.23-ALL NFS patches. Joe --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
kernel panic on open-iscsi login to target
Hi folks: I have a Ubuntu 7.10 machine with a 10 GbE card connected to a target. Same machine running Centos 5.1 connects with no problem to target using 865 code. Booting this machine into Ubuntu (2.6.22-14 kernel by default, though we have also verified that this fails in the same way with a 2.6.23.14 kernel), and then attempting to log in to the same target that just worked with the Centos load (on that same machine), results in an immediate hard kernel lock. No data to screen/ nothing in the logs. Keyboard lights are flashing, but no real data as to what is the cause is available. Any thoughts? Any work arounds? I have tried the 865, the 868 code. Thanks. Joe --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
