Date: Fri, 1 Feb 2002 12:36:50 +0500 From: Sergey Gershtein <sg@ur.ru> To: Peter Jeremy <peter.jeremy@alcatel.com.au> Cc: freebsd-stable@FreeBSD.ORG Subject: Re[2]: Strange lock-ups during backup over nfs after adding 1024M RAM Message-ID: <1427021336.20020201123650@ur.ru> In-Reply-To: <20020131111153.Y72285@gsmx07.alcatel.com.au> References: <20020126204941.H17540-100000@resnet.uoregon.edu> <1931130530386.20020128130947@ur.ru> <20020130073449.B78919@gsmx07.alcatel.com.au> <791310002584.20020130150111@ur.ru> <20020131111153.Y72285@gsmx07.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, January 31, 2002 Peter Jeremy <peter.jeremy@alcatel.com.au> wrote:
PJ> It looks like you've run out of kernel memory. At a quick guess, one
PJ> of the nfsd processes is trying to open a file and can't allocate
PJ> space for another inode whilst holding locks on other inodes. The
PJ> lockup is either due to the lack of KVM, or the inode locks are
PJ> migrating up towards root and gathering more processes under their
PJ> clutches until nothing can run.
PJ> If you monitor the memory usage with "vmstat -m", you should be
PJ> able to see the free memory drop to zero, possibly all eaten by
PJ> the "FFS node".
Here's what "vmstat -m" says about "FFS node":
Memory statistics by type Type Kern
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
...
FFS node152293 76147K 76479K102400K 3126467 0 0 512
...
And this is even without the backup and the lock-up. Definitely "FFS
node" is hitting the limit while all other values are far below
limits. Could you tell me how I can increase "FFS node" limit further?
Regards,
Sergey Gershtein
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?1427021336.20020201123650>