Re: ReadyNas File Store Copy

Most illuminating would be tcpdump logs. Also see if there are any errors in your system logs. The ReadyNAS also can generate a complete set of logs.

Although I am reluctant to quickly point the finger at the "other guy", I did do some browsing on the Neatgear forum and I found them very 'educational'. I think the guys at Infrant are probably better prepared to comment on the cause of failure than us perl mongers.

s//----->\t/;$~="JAPH";s//\r<$~~/;{s|~$~-|-~$~|||s |-$~~|$~~-|||s,<$~~,<~$~,,s,~$~>,$~~>,, $|=1,select$,,$,,$,,1e-1;print;redo}

Comment on Re: ReadyNas File Store Copy

Replies are listed 'Best First'.
Re^2: ReadyNas File Store Copy by jsilva_im (Novice) on Mar 12, 2008 at 13:19 UTC
I tried using Syswrite and it failed as well. There is nothing too odd about the file names as I am specifically copying to "test.pdf". It just seems that it fails on ONLY the larger sized files, roughly greater than 70megs. Even this is random though, because we have had a few normal ones get written without a problem.	[reply]
Re^3: ReadyNas File Store Copy by starbolin (Hermit) on Mar 13, 2008 at 22:11 UTC
More literature search has led to the possibility that the NAS drivers use some socket internally that is timing out on long transfers. That it breaks the same under Syswrite further points to a network stack problem vs an interface problem as once the data is written to the interface it has to be repackaged into MTUs. So block size into the interface is inconsequential. s//----->\t/;$~="JAPH";s//\r<$~~/;{s\|~$~-\|-~$~\|\|\|s \|-$~~\|$~~-\|\|\|s,<$~~,<~$~,,s,~$~>,$~~>,, $\|=1,select$,,$,,$,,1e-1;print;redo}	[reply]