ravensorb
Dabbler
- Joined
- Jan 18, 2012
- Messages
- 37
Hello,
I am running FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty) version of FreeNas and I am in the process of adding additional storage. One of the tasks I am trying to do is move an iSCSI file extent to a new Volume (zfs drive set). Do do this, I setup the new zfs volume, then I logged into the shell, used rsync to copy the file to the new location. Once this was done, I updated the location of the extent in the GUI and restarted the iSCSI service. The issue is, now the iSCSI drive shows up as invalid on the system that was using it (Windows 2012 server -- "The disk structure is corrupted and unreadable").
Based on this I have two questions:
- Should I be able to simple move the file extent? or is that a bad idea
- If i should be able to move, any idea on why I can no longer access it?
I am running FreeNAS-8.3.1-RELEASE-p2-x64 (r12686+b770da6_dirty) version of FreeNas and I am in the process of adding additional storage. One of the tasks I am trying to do is move an iSCSI file extent to a new Volume (zfs drive set). Do do this, I setup the new zfs volume, then I logged into the shell, used rsync to copy the file to the new location. Once this was done, I updated the location of the extent in the GUI and restarted the iSCSI service. The issue is, now the iSCSI drive shows up as invalid on the system that was using it (Windows 2012 server -- "The disk structure is corrupted and unreadable").
Based on this I have two questions:
- Should I be able to simple move the file extent? or is that a bad idea
- If i should be able to move, any idea on why I can no longer access it?