The initiator is strictly a connection mechanism, with no concept of the file system. The workstation operating system handles all file operations, but it does need reliable communication with the target disk. From what we've seen, the initiator maintains the connection to the storage without issue, but as noted in a previous reply, the storage system doesn't seem to support the error detection policy that is set by default in globalSAN, so this protective policy gets disabled. Error 36 is often indicative of trouble with the file system. If you're still able to read from the disk(s), backing up the data (and maintaining current backups) would be a good first step.
Most storage systems (including our own!) do include the error detection policy as added protection for block level communication.
Well, after purchasing the Globalsan iscsi Initiator, I am running into this same error -36 on just about every file I try to copy from my DroboPro. It won't even copy files to my iPhone anymore from iTunes. This is terrible, and renders this software useless to me. What's more alarming to me, is the date of the last post here. Since then, has anyone found a viable solution?
Thank you for the info. It will give me a good start from my experience with Xsan.
Out of interest if we decide to go with SNS San solution iSANmp instead of Xsan to save hardware for the metadata controller. How is it different then Xsan on functionality and performance over Ethernet?
Also, would we have to reformat any RAIDS that are setup as mentioned above with iSCSI? Will iSCSI plus iSANmp work with a Tiger RAID that is connected to a Mac Pro over fiber and share this out over the erthernet using iSCSI?