Displaying 20 results from an estimated 20000 matches similar to: "Zfs pool / iscsi lun with windows initiator."
2011 Feb 23
1
Using Solaris iSCSI target in VirtualBox iSCSI Initiator
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
2007 Oct 05
2
zfs + iscsi target + vmware esx server
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
2010 Oct 11
0
Ubuntu iSCSI install to COMSTAR zfs volume Howto
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
2014 Jul 04
2
iSCSI initiator iqn
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
2012 Sep 28
2
iscsi confusion
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
2009 Dec 05
4
Using iSCSI on ZFS with non-native FS - How to backup.
Hi there.
I''m looking at moving my home server to ZFS and adding a second for backup purposes.
In the process of researching ZFS I noticed iSCSI.
I''m thinking of creating a zvol, share it with iSCSI and use it with my Mac(s).
In this scenario, the fs would obviously have to be HFS+.
Now, my question is:
How would I go about replicating this non-native FS to the backup server?
2007 Jun 19
0
Re: [storage-discuss] Performance expectations of iscsi targets?
Paul,
> While testing iscsi targets exported from thumpers via 10GbE and
> imported 10GbE on T2000s I am not seeing the throughput I expect,
> and more importantly there is a tremendous amount of read IO
> happending on a purely sequential write workload. (Note all systems
> have Sun 10GbE cards and are running Nevada b65.)
The read IO activity you are seeing is a direct
2010 Aug 26
0
zfs/iSCSI: 0000 = SNS Error Type: Current Error (0x70)
Hi,
I''m trying to track down an error with a 64bit x86 OpenSolaris 2009.06 ZFS shared via iSCSI and an Ubuntu 10.04 client. The client can successfully log in, but no device node appears. I captured a session with wireshark. When the client attempts a "SCSI: Inquiry LUN: 0x00", OpenSolaris sends a "SCSI Response (Check Condition) LUN:0x00" that contains the
2007 Jul 04
2
ZFS, iSCSI + Mac OS X Tiger (globalSAN iSCSI)
I have set up an iSCSI ZFS target that seems to connect properly from the
Microsoft Windows initiator in that I can see the volume in MMC Disk
Management.
When I shift over to Mac OS X Tiger with globalSAN iSCSI, I am able to set
up the Targets with the target name shown by `iscsitadm list target` and
when I actually connect or "Log On" I see that one connection exists on the
Solaris
2008 Apr 04
10
ZFS and multipath with iSCSI
We''re currently designing a ZFS fileserver environment with iSCSI based
storage (for failover, cost, ease of expansion, and so on). As part of
this we would like to use multipathing for extra reliability, and I am
not sure how we want to configure it.
Our iSCSI backend only supports multiple sessions per target, not
multiple connections per session (and my understanding is that the
2009 Nov 20
0
hung pool on iscsi
Hi,
Can anyone identify whether this is a known issue (perhaps 6667208) and
if the fix is going to be pushed out to Solaris 10 anytime soon? I''m
getting badly beaten up over this weekly, essentially anytime we drop a
packet between our twenty-odd iscsi-backed zones and the filer.
Chris was kind enough to provide his synopsis here (thanks Chris):
2011 Apr 10
1
iscsi-initiator-utils required in 5.6, loads uneeded modules
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
2008 Feb 05
3
ZFS hang and boot hang when iSCSI device removed
We''re currently evaluating ZFS prior to (hopefully) rolling it out across our server room, and have managed to lock up a server after connecting to an iSCSI target, and then changing the IP address of the target.
Basically we have two test Solaris servers running, and I followed the instructions on the post below to share a zpool on Server1 using the iSCSI Target, and then import that
2015 Jan 10
2
missing backend for pool type 5 (iscsi)
Hi,
I try to define an iscsi pool with virsh but I always get the following
error :
error :internal error: missing backend for pool type 5 (iscsi)
And yet libvirt was compiled with iscsi support :
configure: Storage Drivers
configure:
configure: Dir: yes
configure: FS: yes
configure: NetFS: yes
configure: LVM: yes
configure: iSCSI: yes
configure: SCSI: yes
configure:
2009 Oct 23
1
[PATCH node] Add iSCSI initiator setup option
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
2016 Jun 23
0
CEBA-2016:1284 CentOS 7 iscsi-initiator-utils BugFix Update
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
2016 Aug 02
0
CEBA-2016:1530 CentOS 7 iscsi-initiator-utils BugFix Update
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
2009 Oct 16
0
Issue with LVM and iSCSI lun
Hi all,
Imagine the following situation, you have :
- one ISCSI storage server providing : lun0 and lun1
- the lun0 and lun1 contains a standard installation of Fedora : VM1 and VM2
- the standards installations define two VG VolGroup00 ...
We didn't define LogicalVolume on the node and we attached directly the iSCSI
lun to the VM without making partition or LV in Ovirt.
On the
2016 Oct 04
0
CEBA-2016:1999 CentOS 6 iscsi-initiator-utils BugFix Update
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
2017 Jul 12
0
CEBA-2017:1725 CentOS 6 iscsi-initiator-utils BugFix Update
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