Date: Wed, 27 Aug 2003 17:53:45 +0200 From: Pawel Worach <pawel.worach@telia.com> To: Robert Watson <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: nfs tranfers hang in state getblck or nfsread Message-ID: <3F4CD409.5080703@telia.com> In-Reply-To: <Pine.NEB.3.96L.1030827090202.23748B-100000@fledge.watson.org> References: <Pine.NEB.3.96L.1030827090202.23748B-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: >I have a very similar configuration, but it sounds like I'm not bumping >into the same problem. Are you using NFSv2 or v3, and how many file >systems are you mounting? Are you generally using UFS1 or UFS2? Right >now, I'm mounting a single UFS2 file system was the root, and I believe >right now we always mount NFS roots at NFSv2, which could by why I'm not >seeing the same problem... > >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >robert@fledge.watson.org Network Associates Laboratories > > > Hi Robert! This only seem to happen for nfs over tcp. fstab on the client (/conf/default/etc/fstab) looks like: server:/export/root / nfs ro 0 0 procfs /proc procfs rw 0 0 server:/usr /usr nfs ro,nfsv3,tcp 0 0 server:/usr/home /home nfs rw,nfsv3,tcp 0 0 server:/export /export nfs ro,nfsv3,tcp 0 0 server:/export/data/swap /swap nfs rw,nfsv3,tcp 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 /etc/exports on the server looks like: /export -alldirs -maproot=root -network 192.168.1.0 -mask 255.255.255.0 /export/root -ro -maproot=0 client /export/data/swap -mapall=nobody -network 192.168.1.0 -mask 255.255.255.0 /usr/home client /usr -ro -network 192.168.1.0 -mask 255.255.255.0 filesystems on the server: / magic 11954 (UFS1) time Wed Aug 27 17:34:13 2003 /usr magic 19540119 (UFS2) time Wed Aug 27 17:33:38 2003 /export magic 11954 (UFS1) time Sat Aug 23 23:51:20 2003 /export/data magic 19540119 (UFS2) time Tue Aug 26 07:48:01 2003 I get the errors every time the nfs mounts are not unmounted "cleanly", if the client (which is a laptop and i often forget to plug in the power so the battery dies) dies and the server is rebooted the client boots fine, i.e. no "nfs server not responding errors". So it looks like there is some kind of state mismatch in the nfs server code. rc.conf parameters look like this: server: rpcbind_enable="YES" nfs_server_enable="YES" mountd_enable="YES" nfs_reserved_port_only="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" client: rpcbind_enable="YES" nfs_client_enable="YES" rpc_lockd_enable="YES" rpc_statd_enable="YES" Regards Pawel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3F4CD409.5080703>