When I start my slack 9.1 box with kernel 2.6.2, I get the following
message:

NFS: NFSv3 not supported.
nfs warning: mount version older than kernel

Also - if I try to copy a huge file using a mounted NFS export, it bombs
after copying about 2G, saying that the file is too large.

I have NFS file system support and NFS server support compiled into my
kernel.

What is going on here?

In alt.os.linux.slackware, Robert dared to utter,
> When I start my slack 9.1 box with kernel 2.6.2, I get the following
> message:
>
> NFS: NFSv3 not supported.
> nfs warning: mount version older than kernel

Here's a wild guess. Did you enable NFSv3 support in your kernel?

> Also - if I try to copy a huge file using a mounted NFS export, it bombs
> after copying about 2G, saying that the file is too large.

There may be some limit on the maximum size of an NFS transferred file.
2GB file limits are still somewhat common. Google for more information.

> I have NFS file system support and NFS server support compiled into my
> kernel.

But is it NFSv3 or NFSv4? Do you have client support enabled if you're
using it as a client?

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

__...---I alt.os.linux.slackware, Robert wrote the followin ---...___
> When I start my slack 9.1 box with kernel 2.6.2, I get the following
> message:
>
> NFS: NFSv3 not supported.

Make sure NFSv3 is in your kernel

If that is the case then you have three options:
a)
Search for that error message as well as "file too lart" on google.com
and groups.google.com and see if someone else has solved the problem.
b)
Break the file up into smaller chunks and transfer each block of file
and then reasemble the file.
split -b 1000m $file ;
for f in x* ; do mv $f /destinaiton/ ; done ;
cd /destination/ ;
for f in x* ; do cat $f >> file ; done
ls -l /old/$file /new/$file
#if they are equal then
rm -f /old/file x*
c) ask on a NFS mailing list or group. Not every slackware user uses
NFS[0] but ever NFS user does.


[0] I used to use it. But I found it more unstable than samba. It would
fork and die and cause massive problems all day long on my mp3 setup.

- --
.-')) _ UIN= 66618055 _ (('-. | It's a damn poor mind that
' ..- .:" ) ( ":. -.. ' | can only think of one way to
((,,_;'.;' ';. ';_,,)) | spell a word.
((_.;'*Faux_Pseudo*':._)) | - Andrew Jackson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAN4O/SJec2PH9pbURAu9iAJ0dGFMiQ1h/ZMyUBoPCgLxyuaylAACfRStQ
BL32aOOB+Y9LrqdkJAsylpM=
=XZeu
-----END PGP SIGNATURE-----

Faux_Pseudo <Faux_Pseudo@ip68-230-192-17.rd.hr.cox.net> wrote:

[silliness deleted]

Faux_Pseudo is a coward. Killfile him.

cordially, even to pure shit,

rm