NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tburghart
May 14, 2013Aspirant
Best iSCSI approach on ReadyNAS NV
First, let's skip the responses about the NV not having enough CPU power to use iSCSI effectively :lol: So, I have an old NV with 1GB RAM, 4x750GB 7200 RPM X-RAID, RAIDiator 4.1.10 and iSCSI targ...
chirpa
May 14, 2013Luminary
Maybe try in Flex-RAID mode, create a RAID-? volume, but then delete it and point the iSCSI LUN there. FrontView will complain if it can't create shares on a volume.
I wish there was a raw block device option, but that would have taken too much re-development in FrontView code to handle it properly.
Also, I haven't checked, but can the iSCSI target be a number of sparse disks? Kinda like VMFS being chunked files. So having like (32) 2GB files, all showing as a large 64GB block device. Then maybe the system could cache partial files easier. That could also decrease risk of corruption. If one file gets eaten by EXT4 bugs, only part of the data is gone, not the whole shebang like the stock implementation. One wrong move by EXT4, and a fsck can send your 64GB flat file to lost+found heaven.
I wish there was a raw block device option, but that would have taken too much re-development in FrontView code to handle it properly.
Also, I haven't checked, but can the iSCSI target be a number of sparse disks? Kinda like VMFS being chunked files. So having like (32) 2GB files, all showing as a large 64GB block device. Then maybe the system could cache partial files easier. That could also decrease risk of corruption. If one file gets eaten by EXT4 bugs, only part of the data is gone, not the whole shebang like the stock implementation. One wrong move by EXT4, and a fsck can send your 64GB flat file to lost+found heaven.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!