I don't think this would be a great idea. Not just for the iSCSI targets but
for ESXi datastore use. When a GlusterFS brick fails and resumes, replica
reconstruction (given you use it), will eat almost the whole available
bandwidth, making ESXi fail writing to virtual disks.
I had the same problem in my test environments.
JM2C
Raf
----- Original Message -----
From: "Michael McGlothlin" <michaelm at plumbersstock.com>
To: <gluster-users at gluster.org>
Sent: Monday, April 04, 2011 9:33 PM
Subject: [Gluster-users] iSCSI?
> Has anyone had any success using gluster as a backend for iSCSI
> targets? I want to create 1TB target files which will be shared by
> three iSCSI servers for access by ESXi. I am wondering how gluster
> handles updates to large files such as that - I assume it's smart
> enough to update only the changed blocks and not try to copy the
> entire file around on each update? Also wondering how well it will
> handle multiple servers accessing the same file at the same time. The
> same blocks, iSCSI files, should never be being written to from
> different servers at the same time but the target file would be. Will
> this work? Do I need to do anything special?
>
>
> Thanks,
> Michael McGlothlin
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
>