From: Wakko Warner <wakko@animx.eu.org>
To: Balram Adlakha <b_adlakha@softhome.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1 NFS file transfer
Date: Tue, 29 Jul 2003 09:44:28 -0400 [thread overview]
Message-ID: <20030729094428.B12763@animx.eu.org> (raw)
In-Reply-To: <20030729130400.GA4052@localhost.localdomain>; from Balram Adlakha on Tue, Jul 29, 2003 at 06:34:00PM +0530
> > > 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.
> >
> > I noticed on 2.6.0-test1 that mounting a server using the userspace nfs
> > daemon (v2 I assume) doesn't work very well at all. It was pretty much
> > useless. I rarely ever could get a directory listing. It would just spew
> > "nfs server not responding".
> I'll try with the kernel NFS then, any idea why this happens?
That's what I'd like to know. I have both provide nfsv3 and nfsv4 compiled.
I have not tried it w/o nfsv4 but I do use nfsv3. One of my servers uses
the kernel nfsd with v3 support.
On a side note, I wish I could export / to whoever and everything seen on
the localsystem under / is exported just like the userspace daemon.
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2003-07-29 13:28 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
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 [this message]
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=20030729094428.B12763@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=b_adlakha@softhome.net \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).