Re: Still gettnig NFS client locking up

From: Matt Smith (matt_at_xtaz.co.uk)
Date: 10/31/03

  • Next message: Terry Lambert: "Re: jumbograms (& em) & nfs a no go" 
    Date: Fri, 31 Oct 2003 08:55:49 +0000
To: Robert Watson <rwatson@FreeBSD.ORG>

    Robert Watson wrote:
    > On Tue, 28 Oct 2003, Soren Schmidt wrote:
    >
    >
    >>>I'm now running a kernel/world of October 26th on both NFS client and
    >>>server machines. I am still seeing NFS lockups as reported by several
    >>>people in these threads:
    >>
    >>Me too!!
    >
    >
    > Hmm. I'm unable to reproduce this so far, and I'm pounding several 5.x
    > NFS clients and servers. I've been checking out using CVS over NFS,
    > performing dd's of big files, etc. There must be something more I'm
    > missing in reproducing this. What network interface cards are you using
    > (client, server)? Are you using DHCP on the client or server? What
    > commands trigger it -- what part of the NFS namespace, etc? Are you
    > running the commands as root, or another user?
    >
    > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
    > robert@fledge.watson.org Network Associates Laboratories
    >

    I have 3com cards in both machines. 3c905c's I believe. The xl driver.
    The client has a static IP address configured from rc.conf and the
    server uses dhclient to get a hardwired static address based on MAC.

    I'm running the commands as root. I have noticed that it generally locks
    up when writing to the mount rather than reading as I can do an
    installworld from the NFS server to the client without issues (i think!,
    I've only tried this once). But downloading files into the mount breaks
    very quickly. I guess it could be a filesize thing though. I shall have
    to do some more testing. I was planning on cvsuping and buildworlding on
    saturday again.

    It started happening approx two weeks ago I think? Roughly when I first
    reported it, but NFS had always been solid as a rock before then.

    I can easily reproduce this by doing this:

    [root@womble root]# cd /usr/ports/databases/mysql40-server
    [root@womble mysql40-server]# make fetch
    >> mysql-4.0.16.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
    >> Attempting to fetch from
    ftp://planetmirror.com/pub/mysql/Downloads/MySQL-4.0/.
    Receiving mysql-4.0.16.tar.gz (12830094 bytes): 3%

    (has now locked up)

    [root@womble root]# ls /usr/src
    COPYRIGHT README contrib gnu libexec
    secure usr.bin
    MAINTAINERS UPDATING crypto include release
    share usr.sbin
    Makefile bash.core etc kerberos5 rescue sys
    Makefile.inc1 bin games lib sbin tools
    [root@womble root]# ls /usr/ports

    (has also locked up)

    [matt@womble matt]$ ps wauxl | grep fetch
    root 70213 0.0 0.3 816 660 p3 S+ 8:47AM 0:00.39 make
    fetch 0 63855 0 8 0 wait
    root 70284 0.0 0.5 2604 1212 p3 S+ 8:47AM 0:00.14
    /usr/bin/fetch - 0 70259 0 -8 0 nfsaio

    [matt@womble matt]$ ps wauxl | grep ls
    root 70307 0.0 0.2 772 480 p6 D+ 8:48AM 0:00.01 ls
    /usr/ports 0 70302 0 -1 0 nfsrcv

    [matt@womble matt]$ uname -a
    FreeBSD womble.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Oct 26
    21:14:58 GMT 2003
    root@fraggle.xtaz.co.uk:/usr/obj/usr/src/sys/WOMBLE i386

    [matt@womble matt]$ cat /etc/fstab | grep nfs
    10.0.0.2:/usr/src /usr/src nfs rw,soft,intr 0 0
    10.0.0.2:/usr/obj /usr/obj nfs rw,soft,intr 0 0
    10.0.0.2:/usr/ports /usr/ports nfs rw,soft,intr 0 0

    rc.conf on the client contains:
    ifconfig_xl1="inet 10.0.0.1 netmask 255.255.255.0"
    nfs_client_enable="YES"

    rc.conf on the server contains:
    ifconfig_xl0="DHCP"
    rpcbind_enable="YES"
    nfs_server_enable="YES"
    mountd_enable="YES"

    And this is the uname of the server:
    [root@fraggle src]# uname -a
    FreeBSD fraggle.xtaz.co.uk 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Oct
    26 21:05:49 GMT 2003
    root@fraggle.xtaz.co.uk:/usr/obj/usr/src/sys/FRAGGLE i386

    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Terry Lambert: "Re: jumbograms (& em) & nfs a no go"

    Relevant Pages

    • Errors writing large files via NFS
      ... files larger than a certain size to a NFS server. ... client systems, although the definition of "too large" varies. ... network paths involved, I'm pretty sure we're not seeing a network problem. ...
      (Tru64-UNIX-Managers)
    • Re: Still getting NFS client locking up
      ... > the same NFS lockups. ... > Reading from the server works perfectly all the time. ... > NFS CLIENT: ... in particular, look at traces for any client blocked in NFS, ...
      (freebsd-current)
    • Re: Help me replace some Windows installations
      ... > Possible with untrusted clients in SMB, and trusted clients in NFS. ... >> trust every client that might be connected to this network. ... > Still, user ABC on client, accesses to server with rights of the user ... > which Peter already told you about, or use SMB for Linux to Linux ...
      (comp.os.linux.setup)
    • V210 BGE0@1000FDX
      ... When connecting a server to a Gig interface you need to enable autoneg ... Blocked port after process kill ... NFS oddity ... where hostname is the name of the NFS client which will automount the ...
      (SunManagers)
    • 2.6.9: NFS (+XFS) Problem - Clients getting Stale filehandles.
      ... I'm having a rather vierdNFS Problem. ... We have a disk-backup server ... running an NFS server exporting an XFS filesystem to a number of clients ... Client and server are on the same LAN - no firewall. ...
      (Linux-Kernel)