From: Balram Adlakha <b_adlakha@softhome.net>
To: Ville Herva <vherva@niksula.hut.fi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 NFS file transfer
Date: Tue, 29 Jul 2003 18:30:58 +0530 [thread overview]
Message-ID: <20030729130058.GA3636@localhost.localdomain> (raw)
In-Reply-To: <20030729114838.GS150921@niksula.cs.hut.fi>
On Tue, Jul 29, 2003 at 02:48:38PM +0300, Ville Herva wrote:
> On Tue, Jul 29, 2003 at 04:27:06PM +0530, you [Balram Adlakha] wrote:
> > On Tue, Jul 29, 2003 at 01:48:22AM -0700, Andrew Morton wrote:
> > > Balram Adlakha <b_adlakha@softhome.net> wrote:
> > > >
> > > > I cannot transfer files larger than 914 mb from an NFS mounted
> > > > filesystem to a local filesystem. A larger file than that is
> > > > simply cut of at 914 MB. This is using 2.6.0-test1, 2.4.20
> > > > works fine. Can it be the version of mount I'm using? Its the
> > > > one that comes with util-linux-2.11y.
> > >
> > > Works OK here, with `cp'. How are you "transferring" the file?
> > >
> > > You're sure there is sufficient disk space on the receiving end? (sorry)
> > >
> > > Can you strace the copy operation, see why it terminates?
> >
> > Very strange, It was a 4.9 GB raw mpeg-ps file and I couldn't copy more than 914 mb of it using -test2, even playing the file from the server using mplayer didn't work (and I wasn't smart enough to use strace) then I rebooted with 2.4.20 and the whole file was copied. Now I tried copying a 990 mb wav file and it worked(using -test2). The orginal 4.9 GB file is not on the server now so I'll have to put it there first and then copy it again. It'll take some time on my slow NIC (and the server being a 300 Mhz laptop). I'll email you again, sorry.
>
> Rather than copying a file over, you can create a sparse file very quickly:
>
> touch foo; perl -e 'truncate "foo", 2000000000'
>
> (creates a 2000000000 byte sparse file). Neat thing is, sparse files don't
> take disk space on the server.
>
> Or if you prefer a non-sparse file:
>
> head -c 2000m /dev/zero > foo
>
>
> -- v --
>
> v@iki.fi
Availablity of files is not a problem, theres already a large number of large files that I want to transfer to and from my computer. I didn't know about sparse files, will my NIC be used the same way?
next prev parent reply other threads:[~2003-07-29 13:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 22:59 2.6.0-test1 NFS file transfer Balram Adlakha
2003-07-29 8:48 ` Andrew Morton
2003-07-29 10:57 ` Balram Adlakha
2003-07-29 11:10 ` P
[not found] ` <20030729114838.GS150921@niksula.cs.hut.fi>
2003-07-29 13:00 ` Balram Adlakha [this message]
2003-07-29 12:13 ` Balram Adlakha
2003-07-29 11:24 ` Wakko Warner
2003-07-29 13:04 ` Balram Adlakha
2003-07-29 13:44 ` Wakko Warner
2003-07-29 14:06 ` Trond Myklebust
2003-07-29 14:49 ` Wakko Warner
2003-07-29 14:03 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030729130058.GA3636@localhost.localdomain \
--to=b_adlakha@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@niksula.hut.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox