Also, there are lots of posts about performance, sync writes, and other stuff for iscsi. I'd read up on it. If you go this route, you need to design it right or its performance will suck.
I'm saturating a 1Gb link right now, thats all I can manage anyway.
I did already seem to corrupt an extent file, so I'm a bit worried about iSCSI at this point.
I put a bunch of files on an iSCSI disk from different machines. Disconnected and when reconnecting my entire system just froze up. Tried on my laptop and the exact same thing happend.
Had to delete it and create a new extend from scratch.
I'm hoping that an actual physical volume is more robust.
But I'm a bit afraid of locking up all my files on a block level that might become completely inaccessible when corrupted...
You can not access same iSCSI disk from more then one machine under pain of inevitable data corruption, which is probably what you have got. The only exceptions are specially designed clustered file system, for example, VMware's VMFS. Windows' default NTFS is not clustered! If you want to access iSCSI from Windows, you must create separate disk for every initiator.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.