Date: Fri, 21 Sep 2001 20:10:02 -0700 (PDT) From: Mike Barcroft <mike@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/19479: processes stuck in 'ffsvgt' and 'FFS no' states Message-ID: <200109220310.f8M3A2570482@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/19479; it has been noted by GNATS.
From: Mike Barcroft <mike@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:
Subject: Re: kern/19479: processes stuck in 'ffsvgt' and 'FFS no' states
Date: Fri, 21 Sep 2001 23:07:13 -0400
Adding to Audit-Trail.
----- Forwarded message from Chuck Cranor <chuck@research.att.com> -----
Delivered-To: mike@freebsd.org
Date: Fri, 21 Sep 2001 13:41:34 -0400
From: Chuck Cranor <chuck@research.att.com>
To: freebsd-stable@FreeBSD.org
Cc: mike@FreeBSD.org
Subject: more on 4.4-RELEASE kernel deadlock ("FFS node")
User-Agent: Mutt/1.2.5i
Organization: AT&T Labs-Research
this is a followup to my previous message:
first, the problem i am seeing is almost identical to the one reported
in kern/19479 (see http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19479)
which was closed by mike@freebsd back in july. my data would suggest
that the PR should be re-opened, because it doesn't seem fixed?
i reran a "make release" while having a "vmstat -m | grep 'FFS node'"
running every three seconds in another window. the memory allocation
for "FFS node" is exploding during the "make release"... here is the
last bit of vmstat -m output before the kernel deadlocked:
Memory statistics by type Type Kern
Type InUse MemUse HighUse Limit Requests Limit Limit Size(s)
....
FFS node199352 99676K 99677K102400K 648929 0 0 512
FFS node199871 99936K 99936K102400K 649930 0 0 512
FFS node200457100229K 100229K102400K 651733 0 0 512
FFS node200794100397K 100398K102400K 653082 0 0 512
FFS node200875100438K 100440K102400K 653902 0 0 512
FFS node201466100733K 100733K102400K 655886 0 0 512
FFS node202732101366K 101367K102400K 658611 0 0 512
FFS node203300101650K 101651K102400K 660008 0 0 512
FFS node203851101926K 101926K102400K 661718 0 0 512
FFS node203923101962K 101962K102400K 661927 0 0 512
FFS node204489102245K 102245K102400K 663650 0 0 512
<deadlock here!>
102245K seems like an awful lot of memory for FFS nodes?
what would cause this? does anyone else see very large FFS node
memory allocation during "make release"?
i got a stack trace of the process stuck in "FFS node"... it is
basically:
open
vn_open
namei
lookup
ufs_vnoperate
vfs_cache_lookup
ufs_vnoperate
ufs_lookup
ffs_vget +0x8b
malloc + 0x1a3
tsleep
clearly we are reaching the malloc limit for "FFS node" and hanging.
chuck
----- End forwarded message -----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109220310.f8M3A2570482>