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
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
On Sat, Sep 29, 2012 at 3:09 AM, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris)
opensolarisisdeadlongliveopensola...@nedharvey.com wrote:
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
VMware will properly handle sharing a single iSCSI volume across multiple ESX
hosts. We have six ESX hosts sharing the same iSCSI volumes - no problems.
-Scott
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
Hello,
I think I know the answer to this, but not being an iSCSI expert I am hoping to
be pleasantly surprised by your answers. I currently use ZFS plus NFS to host a
shared VMFS store for my VMware ESX cluster. It's easy to set up and high
availability works great since all the ESX hosts see
Yes, it requires a clustered filesystem to share out a single LUN to
multiple hosts. Vmfs3, however bad of an implementation, is in fact a
clustered filesystem. I highly doubt nfs is your problem though. I'd take
nfs over iscsi and vmfs any day.
On May 23, 2010 8:06 PM, Chris Dunbar -
On May 23, 2010, at 6:05 PM, Chris Dunbar - Earthside, LLC wrote:
Hello,
I think I know the answer to this, but not being an iSCSI expert I am hoping
to be pleasantly surprised by your answers. I currently use ZFS plus NFS to
host a shared VMFS store for my VMware ESX cluster. It's easy
