BTW, it could be you are using NFS v2 which is ONLY 32bit so you have the
4gb filesize limit.
run "nftstat -s" (on the server) and "nfsstat -c" (on the client) to see
what version of NFS you are using (note: what version of NFS you are using
is not related to the transport - udp/tcp).
I use bigger than 4GB files on Linux server/client all the time to move
DVD iso's to machines with better burners...
you are running the 2.6 kernel?
On Tue, 2 Aug 2005, Bryan Whitehead wrote:
What filesystem are you exporting over NFS?
On Tue, 2 Aug 2005, Mark Knecht wrote:
On 8/2/05, Matthew Cline <[EMAIL PROTECTED]> wrote:
> On 8/2/05, Mark Knecht <[EMAIL PROTECTED]> wrote:
> >
> > but how do I know it's being used? And how do I know that the rsize
> > option is being used?
> >
> > Thanks,
> > Mark
>
> Could you watch the traffic between the two using something like
> ethereal? This should tell you which protocol is being used.
>
Hi Matt,
OK, ethereal was pretty easy to use, and it does indeed show that
I'm using TCP for packat transfer. I see a proto=NFS packet followed
by a number of TCP packets with sizes of 8K bytes so this seems to
verify that both options I was looking for ar indeed working.
Thanks!
Unfortunately this means I'm no closer to the root cause of my real
problem which is mythbackend shutting down without warning. It
happened again just a few minutes ago. This all started happening
after I brought this NFS mount on-line as storage for the mythbackend
server. I suppose I'll have to go back to the reduced storage option
(15 hours instead of 120 hours) and make sure that it's really this
disk/PC/network connection.
Thanks again for your help.
Cheers,
Mark
--
Bryan Whitehead
Email:[EMAIL PROTECTED]
--
gentoo-user@gentoo.org mailing list
