D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-343 => Topic started by: iuliand on June 13, 2012, 08:48:28 AM
-
My DNS-343s are configured as Standard Volumes, which should exhibit better performance than your RAID-5 due to the overhead of the RAID array. Furthermore, the DNS-343 uses software RAID, which adds additional overhead than a hardware-based controller.
I'm fine with the SMB speed. I know I can't ask more from this RAID5 software implementation.
What bothers me is the excruciatingly poor NFS performance. It is absolutely not usable with speeds below 1MBps.
I can't wait for you to test NFS performance in order to make a comparison. Thank you for taking the time to test this. I can't tell how much I appreciate it.
-
It looks like NFS is not native to the version of Windows 7 that I have. The native NFS configuration seems to be native only to Enterprise and Ultimate.
As a fallback (and easier test for me to perform), I can enable NFS on my second DNS-343 and add a media directory share to my Boxee Box using NFS and stream some HD video. If the stream doesn't encounter buffer under-run issues, then we know NFS is performing well. Not sure if the Boxee Box shows performance metrics for NW connections.
-
... I can easily connect my second DNS-345 to my Boxee Box using NFS and stream some HD video. If the stream can keep up, then we know NFS is performing well. Not sure if the Boxee Box shows performance metrics for NW connections.
That's way better than nothing. Thanks.
-
That's way better than nothing. Thanks.
I have NFS enabled for a subdirectory containing media. My Boxee Box sees (and accepts) the NFS location as a valid data source, but the Boxee Box says there is no media. The media in this same directory is readily available (and readable) by my Boxee Box via SMB. ???
-
So, you can not even see the media file names? Try creating a sub-folder in the shared one and see if you can see it from boxee. I don't know what boxee allows you to see or how, but I for instance can see the media files and can navigate the folder structure but if I try to play one of the media files it will almost freeze my TViX waiting for the stream to build the buffer, that slow it is.
Is boxee extracting any information from the media files during navigation of the file/folder structure? Maybe it is trying to read something, times out because of the low speed and then show the error?
-
So, you can not even see the media file names? Try creating a sub-folder in the shared one and see if you can see it from boxee. I don't know what boxee allows you to see or how, but I for instance can see the media files and can navigate the folder structure but if I try to play one of the media files it will almost freeze my TViX waiting for the stream to build the buffer, that slow it is.
Is boxee extracting any information from the media files during navigation of the file/folder structure? Maybe it is trying to read something, times out because of the low speed and then show the error?
I will share the parent directory and see where that takes me. :-\
-
No joy. Sharing the parent directory yields the same results (i.e. no media). ???
-
FYI, the Boxee Box pulls directory data through two methods:
- The BB performs daily scans of the source shared directories and saves a local meta data file for offline navigation of the directory contents
- The BB offers real-time browsing of shared directory trees through point and click navigation
Both options see the shared NFS directory tree, but neither discover any content.
-
...
Both options see the shared NFS directory tree, but neither discover any content.
So it seems there is an issue with NFS after all. :(
We need more volunteers to test NFS on DNS-343. I wonder if NFS is working properly on DNS-323 as it should be similar in this regard.
-
Perhaps there is an issue. However, I don't necessarily see the BB as an ideal test platform. At least one other DNS-343 owner should test NFS using a PC running an NFS client (preferably with an application measuring throughput).
-
I encourage everyone reading this topic to make a functionality and speed test of the NFS (Network File System) feature of DNS-343, if they have the means to do it.
For details how to configure the NAS and the client please follow this procedure: http://forums.dlink.com/index.php?topic=49112.msg181120#msg181120 (http://forums.dlink.com/index.php?topic=49112.msg181120#msg181120)
We need more feedback in order to conclude if this feature is functioning properly or not. Please also specify the firmware used for the test.
-
I tried different permutations of configuring NFS between my DNS-343s and BB and still no luck. :-\
-
Follow-up. . . .Have any DNS-343 owners successfully implemented NFS? ???
-
Oh, c'mon, no other testers in all this time? :(
-
Oh, c'mon, no other testers in all this time? :(
Not yet. . . Let's get some volunteers here! ;)
-
Here's an interesting thread to check out in the DNS-320 forum. . . . ???
D-link NAS dns 320 NFS sharing not working on Boxee box..is it possible??? (http://forums.dlink.com/index.php?topic=48468)
-
Been a long time since I posted!!!
I still have my DNS-343 and it's been running NFS for some time now.
It's mapped to 3 hosts running ESXi5 and I don't seem to have any speed issues whatsoever.
Starting up servers is fast and responsive, and I don't get any alerts from VMWare about network connectivity or missed heartbeats.
Oh, and this is just my home lab/network, which is why I'm using Cheap and Cheerful DLink :)
I should also mention I'm on 1.04b03
-
Been a long time since I posted!!!
Yes, three and a quarter years is quite a long time ;)
I still have my DNS-343 and it's been running NFS for some time now.
It's mapped to 3 hosts running ESXi5 and I don't seem to have any speed issues whatsoever.
Starting up servers is fast and responsive, and I don't get any alerts from VMWare about network connectivity or missed heartbeats.
Oh, and this is just my home lab/network, which is why I'm using Cheap and Cheerful DLink :)
I should also mention I'm on 1.04b03
I wonder if the firmware version plays into your NFS success, not to mention the inumerable network configuration and networked device variables to consider as well.