Q: enable iscsi read/write cache
Hi, while looking around in google, if found a logfile http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467390, where the iscsi LUN cache is enabled, read+write: Feb 21 22:19:15 localhost kernel: sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA My dmsg tells me a not enabled write-cache: May 5 20:48:00 xen04 kernel: scsi190 : iSCSI Initiator over TCP/IP May 5 20:48:01 xen04 iscsid: connection189:0 is operational now May 5 20:48:02 xen04 kernel: scsi 190:0:0:0: Direct-Access SUN SOLARIS 1PQ: 0 ANSI: 5 May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] 10485726 512-byte hardware sectors (5369 MB) May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] Write Protect is off May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] 10485726 512-byte hardware sectors (5369 MB) May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] Write Protect is off May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA May 5 20:48:02 xen04 kernel: sdh: sdh1 May 5 20:48:02 xen04 kernel: sd 190:0:0:0: [sdh] Attached SCSI disk May 5 20:48:02 xen04 kernel: sd 190:0:0:0: Attached scsi generic sg11 type 0 M Question: Who can i enable the cache ? hdparms does not work: [EMAIL PROTECTED] /var/log]$ hdparm -W 1 /dev/sdh /dev/sdh: setting drive write-caching to 1 (on) SG_IO: bad/missing ATA_16 sense data:: 70 00 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_DRIVE_CMD(setcache) failed: Input/output error HDIO_DRIVE_CMD(identify) failed: Invalid argument regards Danny --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Compiling openiscsi against self-compiled-xen ?
Hi Tomasz (or maybe other who can help ??) could you compile openiscsi for a self-compiled xen ? Could your please so kind and tell me, how to modify the xen-source-directory structure and/or the openiscsi-source-directory structure (copy/move/edit) to build openiscsi from scratch. For compile xen, i did hg clone http://xenbits.xensource.com/xen-3.2-testing.hg cd xen* make -j8 world make -j8 install make -j9 linux-2.6-xen-install mkinitrd /boot/initrd-2.6.18.8-xen.img 2.6.18.8-xen # and edit /boot/grub/menu.lst But how can i compile openiscsi ? wget http://www.open-iscsi.org/bits/open-iscsi-2.0-869.tar.gz # tar xfvz open-iscsi-2.0-869.tar.gz cd open-iscsi-2.0-869 make KSRC=/root/xen-3.2.1/xen3.2.1/build-linux-2.6.18-xen_x86_64 # or make # or make install # or make KSRC=/root/xen-3.2.1/linux-2.6.18-xen.hg does not work ... because of the 2-tree-xen-directory structure ... Merci for your information regards Danny On 23 Mai 2007, 19:08, Tomasz Chmielewski [EMAIL PROTECTED] wrote: Mike Christie schrieb: Tomasz Chmielewski wrote: Tomasz Chmielewski schrieb: I'm having hard time trying to compile Open-iSCSI (2.0-754) withXen3.1 (source package, 2.6.18 kernel). The kernel part build of Open-iSCSI complains about kernel not supported - which one can understand, asXenhas a bit curious build system and several separated kernel sources. Does anyone have a short recipe on how to compile Open-iSCSI withXen3.1? I looked at the kernel/Makefile, and it looks like it would be enough to copy all kernel/2.6.16-2.6.19/*.c and kernel/2.6.16-2.6.19/*.h files intoXen3.1 kernel source to integrate it permanently - am I correct? It might not work because the sources in the open-iscsi.org/svn release are modified to use the headers from the release and not the ones with the kernel you are building against. And I think the include statements that are coded will not pick things up correctly if you just move the files around. Yes, I also had to copy the content of include/ directory to drivers/scsi/, and modify one file there. I thinkXencompiled, I still have to check tomorrow if it works (Xen 3.1 uses kernel 2.6.18). -- Tomasz Chmielewskihttp://wpkg.org --~--~-~--~~~---~--~~ 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: Compiling openiscsi against self-compiled-xen ?
Hi, i open a commercial request for this task, because i'm not able to fix this problem. https://www.getafreelancer.com/projects/Linux/Compiling-openiscsi-for-xen.html I will post the results to the xen+openiscsi community. regards Danny --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
open-iscsi performance test
Hi, i run a performance-test on a) our native solaris snv90 system AND b) on an exported volume from this solaris-snv90 to an xen04-fedora- core8 using open-iscsi 2.0-869 *** bonnie @ native storage10 (blade16) against pool1 @ 100GB-EVA- RAID10-LUN @diskgroup2 Version 1.03c --Sequential Output-- --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP storage108G 118090 65 98855 17 74481 17 153372 95 251149 20 1037 2 *** bonnie @ xen04, iscsi-import von 20GB-Volume @ solaris exorted Volume @ 100GB-EVA-RAID10-LUN @diskgroup2, Ethernet: 1GB, jumboframes enabled on both systems Version 1.03 --Sequential Output-- --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP xen04.test.softw 1G 54601 95 126731 23 43890 7 47820 93 116211 12 8979 18 I think, the limitation is the iscsi-implementation of solaris or openiscsi ... Is there a possibility to get the iscsi-benchmark closer to the native HDD-benchmark ? regards Danny --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
