iSCSI with fvdw

[hardy74]

Great that it worked. I will test, probably early next week.

You can read & write ext3 from Windows:http://tombuntu.com/index.php/2007/08/14/ext3-file-systems-in-windows/. Tried it with another driver a few years ago and it worked without any problems, even though that was ext2, but ext3 should not be a problem. But you never know with Windows.

If this fully works and it would make the Lacie shares (or "mounts" now) indexable from Win, there will be other interested people.

I will also have a decision to make, because already bought Copernic Desktop Search yesterday... which to use then...

[fvdw]

thanks for this link

I tried and could indeed read the nwsp2 disk on windows :o

ps I needed to use as entry /dev/sda and not just one partition. this ext2 program but also windows disk manger needs a partition table
After that I assigned to individual partition drive letters.

ext2mgr1.JPG

[hardy74]

I still plan to try this. But life has intervened some and the try is postponed temporarily.

[fvdw]

I already tried it , it works ;) I even added a iscsi client in the firmware

[uelpenich]

I understand that the iscsi protocol delivers to windows clients some advantages compared to the smb protocol.

Questions:
if I connect to a server disc via iscsi protocol, ist it still sharable (can be mounted by another computer / user at the same time) ?
if I want to change protocol from smb to iscsi, is it necessary to copy all data to the iscsi disc or partition?
is it possible to use it mixed, the one computer uses iscsi protocol, the other smb protocol?

[fvdw]

I understand that the iscsi protocol delivers to windows clients some advantages compared to the smb protocol.

Questions:
if I connect to a server disc via iscsi protocol, ist it still sharable (can be mounted by another computer / user at the same time) ?
if I want to change protocol from smb to iscsi, is it necessary to copy all data to the iscsi disc or partition?
is it possible to use it mixed, the one computer uses iscsi protocol, the other smb protocol?

iscsi protocol is not a sharing protocol. If you use it to access a certain source be sure you are the only user accessing it. You should not access one share with different users. One of the reason is the type of file system used. Ext3 is not suitable for this. For instance if you access a partition of the NAS via iscsi and make changes on it the samba server running on the NAS will not see until next reboot. Imagine what will happen when you have modified the same file. To make this work you need a specific file system. (you need to have a cluster aware file system).
The only use I see of iscsi on this NAS is accessing with the NAS a remote iscsi server that runs a dedicate disk for you to store data. So only use the NAS as an iscsi client and not as server.
For sure it is no alternative for samba. Also access settings are complicated and as said it is not really a sharing protocol. If you are not an experienced iscsi user I advice not to use it before knowing all ins and outs to prevent major disaster.

[swamswam_h]

The way I usually work with iSCSI is that on the server a target gets defined. Which is basically a virtual disk (let's say for simplicity's sake that it is a file). This target gets 'shared' with a client which then sees it as an attached disk at block level; as if it were attached to a local controller! So it can be formatted and manipulated any way the 'client' wants. The server has no control over what goes on IN the target it merely makes the target available and grants access if the required conditions are met (permissions/user-pass combination). The way FvdW implemented and tested it - correct me if i'm wrong FvdW - is giving access to the entire data disk. That is quite useful, but somewhat insecure for multiple users or multiple computers and thus tricky. And as he pointed out: it is NOT a sharing protocol. It is meant to attach 'virtual' disks on an iSCSI server to clients as if they were real, local disks on the client. You wouldn't want to share your entire operating system disk on a block level with other people or other computers, would you? Each user/computer gets it's own iSCSI disk.

[Mewtos]

Hi all,

sorry for digging up this old thread.
I've installed the new firmware 17.0 on my NWSP2 an now ISCSI i'snt working anymore.

Problem
After updating to the new firmware, i tryed starting ISCSI with ./iscsi-target start in /etc/.
Result: modprobe: module 'iscsi_trgt' not found

Then i did a modprobe with modprobe iscsi_trgt
Result: modprobe: module 'iscsi_trgt' not found

My suggestion was, that the iscsi_trgt.ko was deleted with the firmware update.
I took a look in /lib/modules/2.6.39.4 and it was actually deleted.
Funny thing is, i've deleted my last full-backup from my NAS 4 days ago and don't remembered when i updated today :doh :hammerhead


So, i tryed to re-download and open the attached ZIP in this Thread "iscsi-target-fvdwsl-10nov2012.zip" but the Archive isnt working anymore.
When i open the ZIP Archive with Winrar, i get an "This Archive is broken" and i can't copy the file iscsi_trgt.ko


Is there any chance, that you can re-upload this file?
Or is there another link, that i can use? :please

Thank you in andvance
Mewtos

[Jocko]

Hi Newtos,

So, i tryed to re-download and open the attached ZIP in this Thread "iscsi-target-fvdwsl-10nov2012.zip" but the Archive isnt working anymore.
When i open the ZIP Archive with Winrar, i get an "This Archive is broken" and i can't copy the file iscsi_trgt.ko

It is a good thing as you should not use a module compiled on the kernel version 2.6.39.4 with another kernel version. Currently the firmware uses version 4.6.6 !

So we need to compile a new version for scsi_trgt module. We did not do it as we believed this feature was not used.

I think fvdw will do it.

[Mewtos]

Hi Jocko,

thank you for your fast answer.
Good thing to hear, that it will be compiled soon for 4.6.6 :)
I've actually tryed, copying the iscsi_trgt.ko from the module folder 3.14.2 into the module folder 4.6.6, but it didn't work anyway :whistle

I am using the ISCSI-Target with several LUNs to provide some Disks for my VMs on my Hypervisor.
So, I am looking forward to use ISCSI-Target again with the new firmware and with the speed improvement due to the new firmware.

Greetings,
Mewtos