From owner-freebsd-questions@FreeBSD.ORG Mon Apr 30 19:20:49 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46132106564A for ; Mon, 30 Apr 2012 19:20:49 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id B35A18FC1D for ; Mon, 30 Apr 2012 19:20:48 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SOw9O-0004IQ-CE for freebsd-questions@freebsd.org; Mon, 30 Apr 2012 21:20:46 +0200 Received: from np-19-75.prenet.pl ([np-19-75.prenet.pl]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Apr 2012 21:20:46 +0200 Received: from jb.1234abcd by np-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 30 Apr 2012 21:20:46 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb Date: Mon, 30 Apr 2012 19:20:37 +0000 (UTC) Lines: 39 Message-ID: References: <201204301136.q3UBa8fj083478@mail.r-bonomi.com> <4F9EC5E9.6060604@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: sea.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 79.139.19.75 (Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20100101 Firefox/10.0.2) Subject: Re: UFS Crash and directories now missing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Apr 2012 19:20:49 -0000 Alejandro Imass p2ee.org> writes: > ... > Thanks for pointing a plausible cause. What I have done so far is > limit the offending jail to a specific cpuset and I wanted to add > another disk to avoid contention with other jails. MySQL not only > consumes the whole CPUs but also limits the whole drive, while it's > doing some crazy full scan query on a very large database. > ... I would strongly suggest that you file a PR for nullfs, with included reference to that PR#147420 I mentioned. There is enough of circumstancial evidence. I think there is a chance that a jail panic (corrupted fs or "nullfs path translation") may be the cause of MySQL going bananas. Anyway, the more similar reports they receive the better a chance they will discover any problems, if any. It would be good if you read these sections: JAIL(8) Setting up the Host Environment - a potential for mixing up traffic of same services in host env and jail env. Jails and File Systems - multiple jails sharing the same file system can influence each other. Hierarchical Jails - jail names reflect the hierarchy, but jids on the other hand exist in a single space, and each jail must have a unique jid. BUGS NOTES JEXEC(8) BUGS (ref to JAIL(8), Hierarchical Jails) jb