Date: Wed, 24 Dec 2008 18:24:38 +0300 From: pluknet <pluknet@gmail.com> To: "FreeBSD Stable Mailing List" <freebsd-stable@freebsd.org> Subject: Re: process stuck in vmopar Message-ID: <a31046fc0812240724y4899a801o5b46ecf58f270c7@mail.gmail.com> In-Reply-To: <a31046fc0812240554m1f5ec7b0t12988f5023a6d273@mail.gmail.com> References: <a31046fc0812240423g37455713h76eef8842459f06c@mail.gmail.com> <a31046fc0812240554m1f5ec7b0t12988f5023a6d273@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
2008/12/24 pluknet <pluknet@gmail.com>: > 2008/12/24 pluknet <pluknet@gmail.com>: >> Server version: Apache/2.2.11 (Unix) built from sources. >> >> After issuing kill -9 process stuck in vmopar state forever. >> aaa301 2313 0.0 0.0 0 8 ?? DE 3:10PM 0:00.01 >> /home/aaa301/myb vmopar >> >> System: FreeBSD 6.2 i386. >> > > One important note. > Kernel is built with options QUOTA, and this problem triggered > only when this user is overquoted (usage > quota and limit). A bit later various processes begin to stuck in "ufs" state. > >> Any hints? >> -- wbr, pluknet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0812240724y4899a801o5b46ecf58f270c7>