similar to: Solaris 10 5/09 ISCSI Target Issues

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

Starting from this thread: http://www.opensolaris.org/jive/thread.jspa?messageID=118786&#118786 I would love to have the possibility to set an ISCSI alias when doing an shareiscsi=on on ZFS. This will greatly facilate to identify where an IQN is hosted. the ISCSI alias is defined in rfc 3721 e.g. http://www.apps.ietf.org/rfc/rfc3721.html#sec-2 and the CLI could be something like: zfs set

Hi, are there currently any plans to make an iSCSI target created by setting shareiscsi=on on a zvol bindable to a single interface (setting tpgt or acls)? I can cobble something together with ipfilter, but that doesn''t give me enough granularity to say something like: ''host a can see target 1, host c can see targets 2-9'', etc. Also, am I right in thinking without

I apologize if this has been covered before. I have not seen a blow-by-blow installation guide for Ubuntu onto an iSCSI target. The install guides I have seen assume that you can make a target visible to all, which is a problem if you want multiple iSCSI installations on the same COMSTAR target. During install Ubuntu generates three random initiators and you have to deal with them to get things

Hey all, I''m setting up a ZFS based fileserver to use both as a shared network drive and separately to have an iSCSI target to be used as the "Hard disk" of a windows based VM runninf on another machine. I''ve built the machine, installed the OS, created the RAIDZ pool and now have a couple of questions (I''m pretty much new to Solaris by the way but have been

I''m still trying to find a fix/workaround for the problem described in Unable to mount root pool dataset http://opensolaris.org/jive/thread.jspa?messageID=492460 Since the Blade 1500''s rpool is mirrored, I''ve decided to detach the second half of the mirror, relabel the disk, create an alternative rpool (rpool2) there, copy the current BE (snv_134) using beadm

Does opensolaris iSCSI target support SCSI-3 PGR reservation ? My goal is to use the iSCSI LUN created by [1] or [2] as a quorum device for a 3-node suncluster. [1] zfs set shareiscsi=on <storage-pool/zfs volume name> [2] iscsitadm create target ..... Thanks, -- leon This message posted from opensolaris.org

Not sure where to put this but I am cc''ing the ZFS - discussion board. I was successfull in creating iscsi shares using ZFS set shareiscsi=on with 2 thin provisioned partitions of 1TB each (zfs create -s -V 1tb idrive/d1). Access to the shares with an iscsi initiator was successful, all was smooth, until the reboot. Upon reboot, the console reports the following errors. WARNING:

Hi I have looked at google about this error as well as in ruby on rails forums, but I can not specifically locate the exact problem and the solution for it. Basically, I successfully installed ruby 1.8.4 on HP-UX 11.11 with rails gem. But unfortunately whenever I try to create a test application by using "rails testapp", I am getting the follwing errror: $ rails testapp

Just installed Nexenta and I''ve been playing around with zfs. root at hzsilo:/tank# uname -a SunOS hzsilo 5.11 NexentaOS_20070105 i86pc i386 i86pc Solaris root at hzsilo:/tank# zfs list NAME USED AVAIL REFER MOUNTPOINT home 89.5K 219G 32K /export/home tank 330K 1.78T 51.9K /tank tank/iscsi_luns 147K

Hi, I have a zfs volume that''s exported via iscsi for my wife''s Mac to use for Time Machine. I''ve just built a new machine to house my "big" pool, and installed build 129 on it. I''d like to start using COMSTAR for exporting the iscsi targets, rather than the older iscsi infrastructure. I''ve seen quite a few tutorials on how to use

Rick McNeal and I have been working on building support for sharing ZVOLs as iSCSI targets directly into ZFS. Below is the proposal I''ll be submitting to PSARC. Comments and suggestions are welcome. Adam ---8<--- iSCSI/ZFS Integration A. Overview The goal of this project is to couple ZFS with the iSCSI target in Solaris specifically to make it as easy to create and export ZVOLs

Hi Everyone, I am sure this question has been asked many time before but I really could not get a good solution. The problem I am having is that the application I wrote is acting very slow. For example for the production database, the query I make takes about 3-4 minutes. The application connects to 2 oracle databases(on a remote location) and gets information based on a given search criteria.It

CentOS Errata and Bugfix Advisory 2016:1284 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1284.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 8e44f277f695473fd93e4e46f507973bb20c14a3d690493b9d006969831f5a5b iscsi-initiator-utils-6.2.0.873-33.el7_2.1.i686.rpm

CentOS Errata and Bugfix Advisory 2016:1530 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1530.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 684e67a738b7dce51fd91736f404ec13e2816f48d8474478ac10336b93c03a0e iscsi-initiator-utils-6.2.0.873-33.el7_2.2.i686.rpm

CentOS Errata and Bugfix Advisory 2016:1999 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-1999.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 99e4b99cf132eac84807aea4eaaa2fb498b390a138ec89bc6a6342e3ae55546b iscsi-initiator-utils-6.2.0.873-22.el6_8.i686.rpm

CentOS Errata and Bugfix Advisory 2017:1725 Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1725.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bb20f5019d41d5a7e53b75e8955288aa082ec9c50f924e762ccbe8a96623154b iscsi-initiator-utils-6.2.0.873-27.el6_9.i686.rpm

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

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

CentOS Errata and Bugfix Advisory 2013:0438 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0438.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8127ade8d17da59c23de745f65003917fcada41924f969c43969804ae4896e5c iscsi-initiator-utils-6.2.0.873-2.el6.i686.rpm