Hey everyone:
Here's my info -
NAS4Free 9.1.0.1 (revision 724) x64-embedded; ALASKA A M I Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz 10240MiB RAM
I have created an iSCSI target per most docs, and I've connected a Win2003 server to it (server 1). I then formatted the disk, and all was well. Everything is fine, and iOPs testing gives me about 4000 iOPs combined read/write.
Then, I connected a second Win2003 server (server 2) to the same target, the volume shows up in disk manager, and doesn't prompt for formatting. When I open the new disk, I'm able to create files, and see the folders I created by server 1. But when I create folders on that volume from server 2, I can't see them from server 1. When I try to access the "ghost" directories created on server 1 from server 2, I get the error "The file or directory is corrupted and unreadable".
Any help is appreciated.
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
iSCSI Target, two Windows 2003 initiators = corrupt files?
-
rossiFan
- NewUser
- Posts: 2
- Joined: 20 Sep 2013 17:04
- Status: Offline
-
rossiFan
- NewUser
- Posts: 2
- Joined: 20 Sep 2013 17:04
- Status: Offline
Re: iSCSI Target, two Windows 2003 initiators = corrupt file
Answered my own post from this URL: http://doc.freenas.org/index.php/ISCSI#Portals
NOTE: an iSCSI target creates a block device that may be accessible to multiple initiators. A clustered filesystem is required on the block device, such as VMFS used by VMWare ESX/ESXi, in order for multiple initiators to mount the block device read/write. If a traditional filesystem such as EXT, XFS, FAT, NTFS, UFS, or ZFS is placed on the block device, care must be taken that only one initiator at a time has read/write access or the result will be filesystem corruption. If you need to support multiple clients to the same data on a non-clustered filesystem, use CIFS or NFS instead of iSCSI or create multiple iSCSI targets (one per client).
NOTE: an iSCSI target creates a block device that may be accessible to multiple initiators. A clustered filesystem is required on the block device, such as VMFS used by VMWare ESX/ESXi, in order for multiple initiators to mount the block device read/write. If a traditional filesystem such as EXT, XFS, FAT, NTFS, UFS, or ZFS is placed on the block device, care must be taken that only one initiator at a time has read/write access or the result will be filesystem corruption. If you need to support multiple clients to the same data on a non-clustered filesystem, use CIFS or NFS instead of iSCSI or create multiple iSCSI targets (one per client).