Hi Ed, Chip, Thanks for the responses, it was basically to see whether people had been having any compatibility issues with Oi as backend storage. We've seen datastore disconnects in the ESXi hosts over both iSCSI and NFS, and it seemed odd that there'd be the same problems across both protocols. Didn't really show up in testing and I've seen other people running this kind of setup without issue, so it was really a question to see if there were any other people seeing the same thing. At the same time as the hosts were seeing disconnects we had other machines using the same iSCSI targets without any errors at all, so it is all a bit odd.
Thanks, James On 10 Aug 2013, at 14:32, Edward Ned Harvey (openindiana) <openindi...@nedharvey.com> wrote: >> From: James Relph [mailto:ja...@themacplace.co.uk] >> Sent: Saturday, August 10, 2013 6:12 AM >> >> Is anybody using Oi as a data store for VMware using NFS or iSCSI? > > I have done both. What do you want to know? > > I couldn't measure any performance difference nfs vs iscsi. Theoretically, > iscsi should be more reliable, by default setting the refreservation and > supposedly guaranteeing there will always be disk space available for writes, > but I haven't found that to be reality. I have bumped into full disk > problems with iscsi just as much as nfs, so it's important to simply monitor > and manage intelligently. And the comstar stuff seems to be kind of > unreliable, not to mention confusing. NFS seems to be considerably easier to > manage. So I would recommend NFS rather than iscsi. > > _______________________________________________ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
