From: Chuck Campbell <campbell@accelinc.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: campbell@accelinc.com, linux-kernel@vger.kernel.org
Subject: Re: NFS problem in 2.4.21 (RHEL ES 3 upd 2)
Date: Mon, 7 Mar 2005 13:08:49 -0600 [thread overview]
Message-ID: <20050307190849.GB18702@helium.inexs.com> (raw)
In-Reply-To: <1110218547.11489.32.camel@lade.trondhjem.org>
On Mon, Mar 07, 2005 at 01:02:27PM -0500, Trond Myklebust wrote:
> må den 07.03.2005 Klokka 10:37 (-0600) skreiv Chuck Campbell:
> > I've just built a cluster of dual Opteron boxes, running RHEL 3 update 2
> > x86_64 OS.
> >
> > I have problems creating files larger than 2GB on an NFS mounted filesystem.
> >
>
> Are you perhaps using NFSv2? If so, I suggest you try NFSv3, as the
> NFSv2 protocol does not support 64-bit file sizes.
OK, that fixed it. It certainly wasn't apparent from the docs I plowed
through for the last two days, and I never turned up that gem on Google
either.
Even the NFS-howto didn't point this out, so I'll submit some update info
to them. Sorry for the noise.
-chuck
prev parent reply other threads:[~2005-03-07 19:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 16:37 Chuck Campbell
2005-03-07 18:02 ` Trond Myklebust
2005-03-07 19:08 ` Chuck Campbell [this message]
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=20050307190849.GB18702@helium.inexs.com \
--to=campbell@accelinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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
all inboxes | Powered by JetHome®