From mint-bounce@lists.fishpool.fi Mon Feb 9 17:41:31 2009 To: From: Peter Slegg Subject: Re: [MiNT] NFS server Reply-To: Peter Slegg X-Mailer: MyMAIL Rev:1.91.13668 (Atari/(STiK/STinG/GlueSTiK)) X-Hardware: Atari Milan MIME-Version: 1.0 Date: Sun, 9 Feb 2009 22:20:56 +0200 (GMT) Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <000139ff.019a76d63a48@smtp.freeola.net> References: <0005fe94.014fc422ac64@mail.gmx.net> In-Reply-To: 0005fe94.014fc422ac64@mail.gmx.net X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: p.slegg@scubadivers.co.uk Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n19MfP0L007832 > I found out more: > there seems to be a 'magical filesize barrier' when copying files to server (Falcon CT60/MinT)- > from No.2-Falcon to server, maximum filesize is 1360 bytes, one byte more and the copyaction aborts. > From Linux-PC to server, max. filesize is somewhere between 27000 bytes and 28000 bytes, > copyaction aborts with 'Input/output error' in bash. > Sometimes the size of the file which is (partly) saved on server now is correct, but the file > is not readable (or only shows empty bytes when opened with qed); sometimes the filesize is only a > multiple of 1024 (most 8192). > I hope we can sort this out. > > Thanks for your reply, > Lars > > This sounds similar to a problem I had with Mint 1.16 that didn't occur with 1.15.12 Whenever I sent an email biiger than a certain size it would terminate without sending the entire email. Smaller ones worked fine. I eventually found a "fix" by altering the MTU size. It should be in the FreeMint mail archive. Regards, Peter