From owner-freebsd-stable Thu Apr 11 5:27:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from monkey.sunet.ru (monkey.sunet.ru [217.174.96.78]) by hub.freebsd.org (Postfix) with ESMTP id 49F5037B405 for ; Thu, 11 Apr 2002 05:27:33 -0700 (PDT) Received: (from yura@localhost) by monkey.sunet.ru (8.11.1/8.11.1) id g3BCP5o78191 for stable@freebsd.org; Thu, 11 Apr 2002 16:25:05 +0400 (MSD) (envelope-from yura) Date: Thu, 11 Apr 2002 16:25:05 +0400 (MSD) From: yura Message-Id: <200204111225.g3BCP5o78191@monkey.sunet.ru> To: stable@freebsd.org Subject: m_clalloc failed... (network problem) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi hi. A while back my freebsd4.5-release-p2 has started to give these errors when working with nfs (client): Apr 11 11:32:18 flash /kernel: m_clalloc failed, consider increase NMBCLUSTERS value Apr 11 11:32:18 flash /kernel: fxp0: cluster allocation failed, packet dropped! Apr 11 11:32:19 flash last message repeated 27 times Apr 11 11:32:20 flash /kernel: m_clalloc failed, consider increase NMBCLUSTERS value Apr 11 11:32:20 flash /kernel: fxp0: cluster allocation failed, packet dropped! Apr 11 11:32:20 flash last message repeated 5 times [many many of the similar has been skipped] I mount over nfs and try to copy a large file: $ sudo mount -t nfs machine:/data/dir /mnt $ cp /mnt/gone60sec.avi . When the file grows to about 9.5 megs the fxp0 begins the swear. If, after a while, the operation continues, it falls into panic. It never happened on this or any other machines I've seen in our network.. although mine is the only with R4.5-P2 system, I guess that might be the problem. I don't know. However, this operation stops those fxp0 error at once: $ sudo killall nfsiod I would appreciate if somebody could give any hints in this situation! Thanks in advance. -- Yura Ushakhow Moscow, Russia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message