From owner-freebsd-questions@FreeBSD.ORG Thu May 3 18:27:22 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 5586F106566B for ; Thu, 3 May 2012 18:27:22 +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 090D88FC0C for ; Thu, 3 May 2012 18:27:21 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SQ0kG-0002tv-Vj for freebsd-questions@freebsd.org; Thu, 03 May 2012 20:27:16 +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 ; Thu, 03 May 2012 20:27:16 +0200 Received: from jb.1234abcd by np-19-75.prenet.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 May 2012 20:27:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: jb Date: Thu, 3 May 2012 18:27:05 +0000 (UTC) Lines: 42 Message-ID: References: <201204301136.q3UBa8fj083478@mail.r-bonomi.com> <4F9F1551.5040003@dichotomia.fr> 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: Thu, 03 May 2012 18:27:22 -0000 Alejandro Imass p2ee.org> writes: > ... OK. There is this anomaly in your troubled jail. Because I have not been familiar with ezjail so I am learning it now as we go. I will suggest to you some steps by intuition, and you have to judge for both of us how to do it and what's appropriate. Feel free to give feedback anytime. I understand that this troubled jail can be stopped any time without any problems to your clients. Just in case do a backup of it with ezjail admin entry. Use ezjail admin entries by the way (no 'mv', 'cp', etc). I look at an ezjail tutorial right now and see the following: ezjail Default File Locations /usr/jails/ : Default location to store base jail system template. /usr/jails/flavours/ : Customization for each jail can be done via flavours. For e.g. adding default /etc/resolv.conf file or updating existing /etc/make.conf can be done here. /usr/jails/basejail/ : Base jail will be exported and mounted as read only for each jail. This will save disk space. /usr/local/etc/rc.d/ezjail.sh : Stop / Start / Restart jails script. /usr/local/etc/ezjail.conf : Configuration file for ezjail script. contains settings that control the operation of the ezjail rc script. It is also read by the ezjail-admin utility to figure out where it should perform its actions. /usr/local/etc/ezjail/ : All your jail configuration files are stored here. Now, your task is to figure out where your mounts are configured for that jail, those that are present in the 'mount' output. After that you would stop that jail and delete it (assuming no problem to your customer service) to get rid of those lines in mount output. The reconfigure that jail properly anew (do not use backup for this !) and create it again, check the 'mount' output to see proper sequence of mounts. Then restart the jail and see how it goes. Give us feedback as you go so we can follow you. jb