Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
When I do backups to the DNS-323 the backup is broken into pieces because of an apparent 2GB file size limit. I am assuming this is an artifact of the very OLD version of SAMBA used in the firmware. I looked at the source code and I believe that it is SAMBA 2.2.8a. What is that about 2 years old?
I stand corrected, from the SAMBA website:
===========================================
What's new in Samba 2.2.8a - 7th April 2003
===========================================
So a SAMBA version over three years old. No wonder there is a 2GB file limit. Looking at the SAMBA version history there are also known security issues with this old a version.
Has anyone attempted to compile a newer version of SAMBA for the DNS-323?
Offline
I do not see any limitation in FW 1.02, RAID 1, ext2.
# ls -l E06*
-rwxrwxrwx 1 nobody 501 2994030592 Feb 8 2006 E06AXLRD1.iso
# pwd
/mnt/HD_a2/Storage
Offline
I had no problem storing a 4.3GB DVD ISO on the DNS-323
Offline
I does seem to be strictly a bi-product of Backup-My-PC. Copying a 16GB backup image from my firewire drive to the DNS-323 worked. HMMMMMMM.......
Offline
I had a similar issue. If I mount the drive via smbmount from a linux workstation and use rsync to copy, it failes on files larger then 2gb. If I use a windows pc the same files work.
go figure..
Offline
I was unaware of the 323 until today when I returned a DSM-G600. Even with the latest FW I was having problems copying large files (over 2GB). D-Link tech support were as useless as they could be (on top of a horrible VOIP connection to India).
I want a NAS to store general media (music, photos) and my PVR TV shows. I've read a couple posts on here that seem to indicate that with the latest FW and using EXT2 this device should support very large files. But before I try this again (I wasted a lot of time on the G600) I'd just like some confirmation from current users.
btw....the client desktops will be mostly Windows PCs.
Thanks!
Offline
Howdy,
I've got 2 DNS323's running on a local network with a half dozen Windoz boxes.
I backup daily to one, using Acronis software (some backups over 15gb) and use the other as MP3 and video storage ( apx 8 thousand files).
I am running 1.02 and ET2 without problems.
I do not use the included MP3 server software, just have the MP3's in alot of directories, with client programs on the PC's streaming the music and video....
Overall I'm very happy with the setup.
DennisB
Offline
DennisB wrote:
... MP3 and video storage ( apx 8 thousand files).
I am running 1.02 and ET2 without problems.
I'd like to know if you have verified the 'apx 8 thousand files'. I'm still on 1.01 using EXT2 and have serious issues with large number of files. When transferring apx 3 thousand files in roughly 260 folders, many of the files went corrupt (named file.ext.bad) and some folders weren't transferred at all.
Before the transfer I created a .sfv file and when the transfer was completed, I performed a check using this .sfv file. The result was no good at all. Some files were corrupted, some directories/files were lost. 95% of the files was transferred without problems, but 5% was somehow lost.
Scandisc reports "No errors on your drive" - right!
D-Link support suggested that I should upgrade to 1.01 (which I'm already are using) and that I should use EXT2 since EXT3 is 'buggy' (I'm already using EXT2) - so their help was not that supportive. 1.02 is not yet available in EU as it's still considered to be beta software here and I still havn't figured out if 1.02 will solve the issue I have ot not.
Offline
Howdy,
Yeah, I've been watching the file count like a hawk.
I had the 1.01 and the 1.01b installed before and dealt with the missing file issues, and the 'can't delete directory' issues.
Once I want to 1.02, formated EXT2 and turned off the Itunes server, I haven't had a problem.
And I've been hitting both drives 24/7 for the last couple weeks. Copy tons of files, large files, all seem to work great.
DennisB
Offline
Hi. I have a DNS323 2*500GB Raid 0, updated to FW 1.02 and reformatted. I can't get files > 2GB to transfer.
This make this unit totaly useless to stream DVDs from. :-(
Just my experience,
Offline
I have copied files 4+ GB in size to my DNS-323 FW1.02 via windows XP file sharing without issue. Raid 1 setup, ext2.
Offline
Hi,
This problem exists only under Windows 2003 or SBS2003
FW: 1.02
Greetings
Werner
Offline
wgreipl wrote:
Hi,
This problem exists only under Windows 2003 or SBS2003
FW: 1.02
Greetings
Werner
In my experience, it also exists under Vista (which is built on w2k3). Is there a known fix for this yet?
Thanks
Justin
Offline
My original post was problems with XP SP2.
Offline
I've experienced a 2GB file limit using Windows explorer of W2K3, but not WXP - I have a 1.98 GB file that will transfer and a 2.01 GB file that will not. The largest file I've transferred from WXP to date is 13 GB
Offline
Ok this is driving me nuts.
I was on 1.01b before upgrading to 1.02
I've only ever used EXT2.
After upgrading to 1.02 I did format everything
From Windows 2003, I can not copy files Greater than 2GB.. unless it's over 4GB and less than 6GB.
The error is always "not enough free disk space"
1.92GB - Success
2.08GB - Fail
2.97GB - Fail
3.05GB - Fail
3.89GB - Fail
3.98GB - Fail
4.04GB - Success
4.18GB - Success
4.98GB - Success
6.58GB - Fail
7.92GB - Fail
7.94GB - Fail
11.8GB - Fail
18.6GB - Fail
23.1GB - Fail
Just ran a quick test and a box I have with Windows 2003 WITHOUT SP1 is able to copy the files just fine.
Note - of the 'success' files, I haven't actually validated the data and done any sort of checksums on them... I can just tell you it didn't error out on a copy attempt.
Offline
Well, somewhat good news here...
I was able to get debian sarge installed and I installed samba inside sarge. I was then able to run samba inside of sarge and then had no problem with any size file. So, the bug is related to Samba it appears. Now I need to figure out how to compile things and create a new samba that I can run outside of sarge with statically linked libraries.
Offline
Installed 1.02b and had my fingers crossed that is would fix the large file problem, but it did not. Using Windows Vista 64bit. Hope they fix this problem soon.
Offline
I hope that you've reported this issue to D-Link. /Apan
Offline
Sure did, I will post their reply on the board when I get it.
Offline
Question asked Dlink: When will a firmware come out that will allow a user to copy files larger then 2 gigs to the DNS 323 using Windows Vista?
Here is Dlink's reply:
"We have a firmware 1.02b this may work out for you but we have fixed this restriction in 1.01 FW. please try the new firmware tho."
Offline
Slammer88 wrote:
Question asked Dlink: When will a firmware come out that will allow a user to copy files larger then 2 gigs to the DNS 323 using Windows Vista?
Here is Dlink's reply:
"We have a firmware 1.02b this may work out for you but we have fixed this restriction in 1.01 FW. please try the new firmware tho."
Seriously? That's a dumb response. So their releases don't contain all subsequent fixes? That's brilliant. Lets make new firmware releases with all different fixes! Why would we incorporate all fixes into one? That's no fun!
Offline
I was able to also now compile samba-2.2.12 (I haven't jumped into 3, its quite different and I wanted the configuration files to stay the same and such for now...) natively (running without debian) and this fixes the problem.
It utilizes the fun_plug and a script to delete the symlinks to the samba files on /sys/crfs (read only) and links them to an area on the hard drive that hosts the new binaries.
As soon as I get everything as solid as I would like, I'll upload it here.
there is a slight possibility this may kill the powersaving feature of shutting down the hard drives, as you're now running processes from the hard drive. There isn't enough space in the ram drive to copy these binaries over...
I'll do more testing, and as I said, when I feel solid with everything I'll put the files up here.
Offline
tobyg wrote:
there is a slight possibility this may kill the powersaving feature of shutting down the hard drives, as you're now running processes from the hard drive. There isn't enough space in the ram drive to copy these binaries over...
USB Flash Drives are cheap. I'd reccomend to store these (and other) files to external, non-mechanical, storage.
Well done, please add this to the Wiki when you're done.
/Apan
Offline
Apskaft wrote:
tobyg wrote:
there is a slight possibility this may kill the powersaving feature of shutting down the hard drives, as you're now running processes from the hard drive. There isn't enough space in the ram drive to copy these binaries over...
USB Flash Drives are cheap. I'd reccomend to store these (and other) files to external, non-mechanical, storage.
Well done, please add this to the Wiki when you're done.
/Apan
I like that idea a lot. So you would still need fun_plug from the HD to load the USB drivers for your USB drive, but then you mount and run everything else off of the USB flash drive. I like it. And if you have a problem, you can just unplug the USB flash drive, reboot, and fun_plug then wouldn't be able to run anything.
The problem I'm faced with right now with running off of the HD is making sure I don't break anything. If I setup my script to copy over key critical files such as samba files and redo symlinks and such, and something goes wrong with Samba, I can't just mount the drive and edit the script. If something goes wrong and telnet doesn't load, and now samba doesn't load, you can be pretty screwed. Personally I already wired in a serial port so I can get right on the console serial port, but not everyone has the luxury of tearing apart their box and wiring in a serial port.
I'll have to think about how I want to implement this in my own setup, and some way to make it safer for users who want to run it off of the HD.
The good news is I ran it all last night and the drives stay powered down just fine when idle. This is with running samba off of the hard drive by just using symlinks referencing the samba files on the HD. When I was previously running samba through debian, it would keep spinning the hard drives back up.
Offline