Re: Diskless client problems

From: Ben Sagal (bmsagal_at_gmail.com)
Date: 10/31/05

  • Next message: rickard: "unsubscribe"
    Date: Mon, 31 Oct 2005 12:42:18 +0200
    To: Daniel Nilsson <daniel@oden.homeip.net>
    
    

    I have fixed the problems with all the error messages, The server was
    using an ancient RTL8029, i replaced it with an e100, and the whole
    network is now flying.

    I still know why it is not using tcp, but this is not so important now.

    Thank You

    Ben.

    On 31/10/05, Ben Sagal <bmsagal@gmail.com> wrote:
    > I have tried to mount it with on tcp, the dhcp sends the following for rootpath:
    > "192.168.1.1:/srv/client,ro,tcp,hard,intr"
    > but the tcp part seams to be ignored by the client,
    >
    > I have confirmed the server can handle tcp since i have been
    > successful in connecting using tcp from another (non-diskless) client.
    >
    > Ben
    >
    > On 31/10/05, Daniel Nilsson <daniel@oden.homeip.net> wrote:
    > > Ben Sagal (bmsagal@gmail.com) wrote:
    > > >
    > > > I have a few diskless clients setup, using a read-only nfs root, and
    > > > with a tmpfs mounted for /var, /home and /tmp. The system regularly
    > > > prints the following messages:
    > > > nfs: server 192.168.1.1 not responding, still trying
    > > > nfs: server 192.168.1.1 OK
    > > > the output from mount on the client is:
    > > > /dev/root on / type nfs
    > > > (ro,v2,rsize=4096,wsize=4096,hard,udp,nolock,addr=192.168.1.1)
    > >
    > > Ben,
    > >
    > > These kinds of issues are usually related to network issues, see
    > > the NFS HOWTO http://nfs.sourceforge.net/nfs-howto/
    > >
    > > NFS is rather sensitive with respect to packet loss, and issues with
    > > the cabling for example quickly results in the messages you are
    > > observing. I would first make sure the /sbin/ifconfig doesn't show
    > > and errors associated with the adapter you are using (a lof of
    > > dropped packets, errors, etc). Check hubs switches and all things
    > > related.
    > >
    > > When running NFS over a wireless link for example, this has been
    > > is a common problem for me, but you can't really make the wireless
    > > connection perfect such that all packets always arrive on time.
    > > Fortunately you can switch to run NFS over TCP instead which makes a
    > > huge difference for wireless links or other high loss networks. If
    > > you are using normal ethernet and can't find the cause, you could
    > > try to run NFS over TCP instead. It's an option on the mount command.
    > >
    > > Hope this helps
    > >
    > > /Daniel
    > >
    > >
    > > --
    > > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
    > > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    > >
    > >
    >


  • Next message: rickard: "unsubscribe"

    Relevant Pages

    • Re: nfs client does not find nfs server
      ... I can find the server now using YAST after deactivating the firewalls ... mount server reported tcp not available, falling back to udp ... 100003 2 udp 2049 nfs ...
      (comp.os.linux.networking)
    • nfs troubles
      ... I'm having trouble getting NFS set up. ... I have nfs-common and nfs-kernel-server installed on the server and nfs-common installed on the client. ... 100000 2 tcp 111 portmapper ... 100000 2 udp 111 portmapper ...
      (Debian-User)
    • Re: mount.nfs internal error
      ... Whenever I try to mount from a server on my LAN, ... Adding a -o udp to the mount still fails ... Linux does not yet support nfs over IPv6, although rpcbind does support IPv6 queries.) ... 100000 4 tcp 111 portmapper ...
      (comp.os.linux.networking)
    • Re: SCO 5.0.7 MP5 network hung up
      ... instead of the server I was reloading. ... The system was still inaccessible via the network. ... It is probably the case, with some minor exceptions, that whatever `tcp ... is still seeing the streams memory leakage with its NIC on IRQ11. ...
      (comp.unix.sco.misc)
    • Re: nfs troubles
      ... I'm having trouble getting NFS set up. ... I have nfs-common and nfs-kernel-server installed on the server and nfs-common installed on the client. ... 100000 2 tcp 111 portmapper ... 100000 2 udp 111 portmapper ...
      (Debian-User)