Thanks for all the help everyone. Looks like I'm going to go with clustering. If NTFS is the issue, I'm curious if any of you have tried other filesystems on Windows servers that support shared volumes, like DataPlow SFS or others?
Thanks again, Mark On Wed, Jul 21, 2010 at 9:06 AM, Andrew S. Baker <[email protected]> wrote: > Exactly. > > Which is where the OP suggested he was headed... > > -ASB: http://XeeSM.com/AndrewBaker <http://xeesm.com/AndrewBaker> > > > On Wed, Jul 21, 2010 at 1:45 AM, Brian Desmond > <[email protected]>wrote: > >> *2008 R2 added CSVs (Cluster Shared Volumes) though which will give you >> this…* >> >> * * >> >> *Thanks,* >> >> *Brian Desmond* >> >> *[email protected]* >> >> * * >> >> *c - 312.731.3132* >> >> * * >> >> * * >> >> *From:* Joseph L. Casale [mailto:[email protected]] >> *Sent:* Wednesday, July 21, 2010 11:07 AM >> >> *To:* NT System Admin Issues >> *Subject:* RE: iSCSI and shared volumes >> >> >> >> Hasn’t anything at all to do with the ini, it’s the filesystem that the >> target exports. >> >> iSCSI is not a file sharing protocol, you likely have already corrupted >> the ntfs filesystem on the 5tb volume you have done with this. >> >> >> >> Although the ini often needs to support scsi reservations (ms ini does) >> the underlying filesystem has to know how to deal with concurrent access, >> vmfs is a cluster aware fs and hence can do this. ntfs is **not** a >> cluster aware fs. >> >> >> >> I sure as hell hope nothing you needed was being exported on that targetJIts >> not a matter of maybe, you have damaged that fs already. >> >> >> >> *From:* Andrew S. Baker [mailto:[email protected]] >> *Sent:* Tuesday, July 20, 2010 8:42 PM >> *To:* NT System Admin Issues >> *Subject:* Re: iSCSI and shared volumes >> >> >> >> This isn't a Microsoft issue. >> >> >> >> Most iSCSI initiators are not set to handle writes to a volume from other >> volumes. >> >> >> *ASB *(My XeeSM Profile) <http://xeesm.com/AndrewBaker> >> *Exploiting Technology for Business Advantage...* >> * * >> >> Signature powered by WiseStamp <http://www.wisestamp.com/email-install> >> >> >> >> On Tue, Jul 20, 2010 at 8:26 PM, Ziots, Edward <[email protected]> >> wrote: >> >> Why I love ESX soo much, don’t have to worry about M$ shared volume issues >> with failover of VM’s and accessing .VMDK and .VMX files from the same >> volume, updating them and likewise. >> >> >> >> Z >> >> >> >> Edward E. Ziots >> >> CISSP, Network +, Security + >> >> Network Engineer >> >> Lifespan Organization >> >> Email:[email protected] <email%[email protected]> >> >> Cell:401-639-3505 >> >> >> >> *From:* Andrew S. Baker [mailto:[email protected]] >> *Sent:* Tuesday, July 20, 2010 8:14 PM >> >> >> *To:* NT System Admin Issues >> >> *Subject:* Re: iSCSI and shared volumes >> >> >> >> Time for plan B. :) >> >> You have correctly surmised the problem. >> >> -ASB: http://XeeSM.com/AndrewBaker <http://xeesm.com/AndrewBaker> >> >> Sent from my Motorola Droid >> >> On Jul 20, 2010 7:30 PM, "Mark Smith" <[email protected]> wrote: >> >> I have a few 2008 R2 servers that are stand alone (not clustered) Hyper-V >> hosts. >> >> They are connected via iSCSI to a single 5TB volume on a DELL/Equallogic >> PE6000 iSCSI target. >> >> The idea is to have the VM's for all the Hyper-V hosts in one volume on >> the PE6000 and have all the hosts access that same volume simultaneously. >> >> I am having a problem in that when one host writes to the volume the other >> hosts don't see the changes. >> >> Should this configuration work as I'm intending or do I need to go with >> clustering in R2 and use CSV (Cluster Shared Volume) ? >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
