similar to: iSCSI experiences

I have a filer running Opensolaris (snv_111b) and I am presenting a iSCSI share from a RAIDZ pool. I want to run ZFS on the share at the client. Is it necessary to create a mirror or use ditto blocks at the client to ensure ZFS can recover if it detects a failure at the client? Thanks, Bruin

Hello all. We recently purchased HP Proliant DL380 G7 server and also a HP Lefthand P4500 G2 24TB iSCSI box. The server itself has Quad Ethernet based on the BCM5709 Chipset from Broadcom (NetXtreme II). My main question is about iSCSI offload mechanism, as iSCSI itself is pretty new to me but I have gotten a good hold on it tho. I have managed to setup and configured our Lefthand box into

Well, Im using an Adaptec Snap 4500 and I've had nothing but problems with it, initially I thought it was an issue with CHAP authentication so I completely disabled authentication and the kernel is still reporting in dmesg and /var/log/messages that it cannot authenticate with the target /boggle... On a side note, I know the iscsi slice works because I can connect to it just fine on Windows XP

I''m testing an Iscsi multipath configuration on a T2000 with two disk devices provided by a Netapp filer. Both the T2000 and the Netapp have two ethernet interfaces for Iscsi, going to separate switches on separate private networks. The scsi_vhci devices look like this in `format'': 1. c4t60A98000433469764E4A413571444B63d0 <NETAPP-LUN-0.2-50.00GB>

Hi, I could not find any option to set iSCSI initiator iqn while using guestfish, although the underlying qemu command has this option. It appears that each time guestfish tries to connect to iSCSI LUN, a randomly generated initiator iqn is being used. This is preventing guestfish to connect to the iSCSI target in our environment as the target allows incoming connection based on the preconfigured

I just updated one of my virtual hosts to 5.6 and on rebooted I spotted an error about iscsi. Which surprised me, since I don't use iscsi. Yet there it is... % rpm -qf /etc/init.d/iscsi iscsi-initiator-utils-6.2.0.872-6.el5 And they're configured to start iscsi 0:off 1:off 2:off 3:on 4:on 5:on 6:off iscsid 0:off 1:off 2:off 3:on 4:on

I am confused, because I would have expected a 1-to-1 mapping, if you create an iscsi target on some system, you would have to specify which LUN it connects to. But that is not the case... I read the man pages for sbdadm, stmfadm, itadm, and iscsiadm. I read some online examples, where you first "sbdadm create-lu" which gives you a GUID for a specific device in the system, and then

How do I go about troubeshooting this? I'm using RHEL 4 update 6. mount: /dev/sdb1 already mounted or /blah busy It's actually an iSCSI LUN (NetApp filer). I successfully configured (ext3) and mounted it, but when I rebooted, the /dev/sdb1 device/partition is seen by the kernel and it shows up with "fdisk -l". Nevertheless I get that error. I've tried

This add an iscsi initiator name setup option to the main menu in ovirt-config-setup and can also be accessed via ovirt-config-iscsi. Also accepts AUTO setup by running ovirt-config-iscsi AUTO and generates a random name as before --- Makefile.am | 1 + ovirt-node.spec.in | 3 ++ scripts/ovirt-config-boot | 4 --- scripts/ovirt-config-iscsi | 56

Thu Jul 7 14:47:23 UTC 2016, m.roth at 5-cent.us wrote: > Hi, folks, > > I installed the iscsi packages, and I *thought* that the first thing to > do was configure /etc/tgt/target.conf. Am I wrong? Did I have to > configure iSNS on the RAID appliance? One thing to make sure you have straight is Target vs. Initiator [2], for me it originally felt like the names were backwards.

Hi All, I'm running KVM host on CentOS 5.6 x64, all of my guests are CO 5.6 x64 as well. I create / run VMs via libvirt. Here are the packages I have: # rpm -qa | egrep "kvm|virt" kvm-83-224.el5.centos python-virtinst-0.400.3-11.el5 kvm-qemu-img-83-224.el5.centos kmod-kvm-83-224.el5.centos libvirt-python-0.8.2-15.el5 etherboot-zroms-kvm-5.4.4-13.el5.centos libvirt-0.8.2-15.el5

I''ve recently upgraded my x4500 to Nevada build 97, and am having problems with the iscsi target. Background: this box is used to serve NFS underlying a VMware ESX environment (zfs filesystem-type datasets) and presents iSCSI targets (zfs zvol datasets) for a Windows host and to act as zoneroots for Solaris 10 hosts. For optimal random-read performance, I''ve configured a single

Hi there, I have one server acting as a iscsi target running windows storage server r2 sp2 and the other server is running centos as an initiator. They are connected to a switch over a 1Gbit ethernet connection. the target is a Dell NF600 and the server running centos is a Poweredge R900. We want to move this configuration to a FC based installation using a Dell QLE2462 HBA (this is the hba we can

Hello, I?m using ZFS to export some iscsi targets for the virtual box iscsi initiator. It works ok if I try to install the guest OS manually. However, I?d like to be able to import my already prepared guest os vdi images into the iscsi devices but I can?t figure out how to do it. Each time I tried, I cannot boot. It only works if I save the manually installed guest os and re-instate the same

We run our IMAP spool on ZFS that''s derived from LUNs on a Netapp filer. There''s a great deal of churn in e-mail folders, with messages appearing and being deleted frequently. I know that ZFS uses copy-on- write, so that blocks in use are never overwritten, and that deleted blocks are added to a free list. This behavior would spread the free list all over the zpool. As well,

I''m posting here as this seems to be a zfs issue. We also have an open ticket with Sun support and I''ve heard another large sun customer also is reporting this as an issue. Basic Problem: Create a zfs file system and set shareiscsi to on. On a vmware esx server discover that iscsi target. It shows up as 249 luns. When attempting to then add the storage esx server eventually

Hello, I'm looking for test users for new iSCSI target software designed for multipath failover cluster nodes. I'm very interested in the virtual machine such as Hyper-V. So I'm also tuning the target for using VMs. I need an environmental report in particular other than FreeBSD 7.1 RELEASE p3 i386/PAE kernel w/ZFS. I welcome the report with other initiators below. If you are

Hi List, I've started looking into iSCSI, and I'm wondering if there is an iSCSI target (I've found the initiator in iscsi-initiator-utils) that ships with CentOS, or if not, what the recommended target would be. I'd like to export either a partition or (preferably) a file-as-a-partition. Yours, -S -- Simen Thoresen, Wulfkit Support, Dolphin ICS

Hi, i have a debian Etch x86_64 with a xen 3.1 on a kernel 2.6.18-xen. I have some DomU with Debian Etch. I installed open-iscsi, configure /etc/iscsi/iscsid.conf: --- node.active_cnx = 1 node.startup = automatic #node.session.auth.username = dima #node.session.auth.password = aloha node.session.timeo.replacement_timeout = 120 node.session.err_timeo.abort_timeout = 10

Running CentOS 5.5 x86_64 on Dell R710 boxes. I have the server(s) configured for bonding/vlan and will be using iscsi to a SAN. I am in the pre-deployment stage so I am just setting up the basic cookie cutter configurations so I haven't initiated the iscsi connection to a SAN yet. While going through the error messages I noticed this error: kernel: bnx2i: iSCSI not supported, dev=ethX.