Date: Tue, 25 Jan 2000 16:53:03 -0800 From: Alfred Perlstein <bright@wintelcom.net> To: thomas@members.ping.de Cc: US FreeBSD Stable Mailing List <freebsd-stable@FreeBSD.ORG> Subject: Re: FreeBSD, Linux and NFS Message-ID: <20000125165303.A26520@fw.wintelcom.net> In-Reply-To: <20000126003948.A476@dante.visionaire.net>; from thomas@visionaire.ping.de on Wed, Jan 26, 2000 at 12:39:48AM %2B0100 References: <20000126003948.A476@dante.visionaire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Thomas Keusch <thomas@visionaire.ping.de> [000125 16:20] wrote:
>
> Hello,
>
> does anybody happen to be running NFS between FreeBSD und Linux
> successfully and painless?
>
> I've got FreeBSD 3.4S cvsupped xmas or one, maybe two days after,
> running as NFS server, while my Linux v2.2.14 box is the client.
>
> On Linux, I mount stuff like this:
>
> $ mount -t nfs -o ro,noauto,user,tcp,rsize=8192,wsize=8192,timeo=14,intr \
> darkstar:/storage /tmp/storage.darkstar
>
> On the FreeBSD side of the universe, I've got this in /etc/rc.conf:
>
> $ grep -e nfs -e mount /etc/rc.conf
> nfs_server_enable="YES"
> nfs_server_flags="-t -n 4"
> mountd_flags="-2 -r"
>
> Ok, so if I get things right, which I think (hopefully) I do, this means
> that Linux mounts NFS filesystems via TCP/IP, the FreeBSD server forces
> NFS v2 via the "-2" switch given to mountd and the 4 nfsd only serve
> stuff via TCP/IP ("-t" argument).
Last time i saw someone trying to use tcp NFS mounts in Linux, thier
box would hang/crash even before the mount came up, I'm sure Linux's
nfs has improved (they even have some sort of lockd going) however
I'd try UDP and see what happens.
> But, stressing my home LAN a little bit the last few days, it happened
> to me three times already that the server simply stops serving the fs
> (or NFS in general, I didn't check before restarting stuff :-( ),
> while it stays perfectly functional in all other ways I can think of.
> Ok, it may be that no new/further NFS exported fs may be mounted by
> remote machines, I don't know yet, but I can get you current if asked
> to. Maybe it is just a regular permission problem that it can't mount
> the fs in question via loopback networking.
I'm not sure I understand, are you saying that:
the linux box can't do any NFS to the freebsd box and:
a) FreeBSD is able to mount its own shares?
Or
b) FreeBSD is _not_ able to mount its own shares?
> Restarting nfsd/mountd, whichever order of starting them, doesn't seem
> to help, on the Linux box processes accessing the NFS fs still hang.
> Having restarted the daemons, I can mount another fs, though.
> (Don't know if this works without restarting, sorry. But I can test..)
>
> *Finally* :-)
> ... finally this is the error message I get on the Linux box syslog:
>
> dante kernel: nfs: server darkstar not responding, still trying
I'd be interested in knowing the output of
ps -alx | grep nfsd
on the freebsd box when this happens.
> Any ideas on that one?
>
> Is my assumption, that _only_ NFS v2 via TCP/IP, *NOT* UDP, will work
> between FreeBSD and Linux, correct? At all? If it ever was?
> (I just seem to have remembered this sort of stuff popping up on the
> lists and v2/tcp NFS being the solution)
I'm not sure how well TCP mounts will work as I mentioned above,
try UDP as mentioned in the other email you got.
Have you tried FreeBSD<->FreeBSD mounts with the same configuration
yet?
> So, is there some help for me?
hopefully yes. :)
> I don't really know where to look at now..
>
> Thanks for your valueable time, if you actually read this far :-))
No, problem, just don't disappear, we'd like to know what's going on. :)
--
-Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000125165303.A26520>