From owner-freebsd-fs@FreeBSD.ORG Fri Jun 14 13:06:42 2013 Return-Path: Delivered-To: fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EFC17928; Fri, 14 Jun 2013 13:06:42 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-lb0-f174.google.com (mail-lb0-f174.google.com [209.85.217.174]) by mx1.freebsd.org (Postfix) with ESMTP id 48E001E20; Fri, 14 Jun 2013 13:06:42 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id x10so577997lbi.33 for ; Fri, 14 Jun 2013 06:06:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/61i0b7zhMma+Wf2YiJn0SDe+BaC8XnCfd2m+7eHpJU=; b=CoGk7IcI0PcqPOmd6thaf6JWHGMG7oNO6x9lSjlDgdpjvGFprMgnXWmcdxMZVANF1v v4b6q97GIpDCfgAQgyEywwEfKb4xbnNBpf7WBanzIAig0ltnvSaRBVMdRGha7oUvx9FK bgmqRlJjozhEz8Rbf8jt1a1XM1/UaWeg6HlUV+nGz0TOXz/cK2IINOzCgTIwfcylcAf4 YCHEh/e7uJhcYppq7JGBG+6rCW+R1cn3WcRkzwUQSstl5WVp553aDmLAJgH/6kjVbTlf KO2YcDFdWRZYb9dOc4iFNBslpXK5ZQEbC9mAq+CrsQfz37GnMAX4aFAW7tiQGZMnIILd FCXQ== X-Received: by 10.112.144.6 with SMTP id si6mr1090609lbb.61.1371215195200; Fri, 14 Jun 2013 06:06:35 -0700 (PDT) Received: from [192.168.1.125] (mau.donbass.com. [92.242.127.250]) by mx.google.com with ESMTPSA id p20sm842159lbb.17.2013.06.14.06.06.34 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 14 Jun 2013 06:06:34 -0700 (PDT) Message-ID: <51BB1559.7050803@gmail.com> Date: Fri, 14 Jun 2013 16:06:33 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:20.0) Gecko/20100101 Firefox/20.0 SeaMonkey/2.17.1 MIME-Version: 1.0 To: Dr Josef Karthauser Subject: Re: Help! :( ZFS panic on boot, importing pool after server crash. References: <301B4131-F677-4B8D-ABF6-A6D269FE604E@gmail.com> <51BAF7E3.4020401@gmail.com> <9AF22029-B753-4D74-A798-11C0A1C55D88@gmail.com> In-Reply-To: <9AF22029-B753-4D74-A798-11C0A1C55D88@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "freebsd-stable@freebsd.org" , fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2013 13:06:43 -0000 14.06.2013 15:51, Dr Josef Karthauser: > On 14 Jun 2013, at 12:00, Volodymyr Kostyrko wrote: > >> 14.06.2013 12:55, Dr Josef Karthauser: >>> Hi, I'm a bit at the end of my tether. > >>> p.s. the config, btw, is a ZFS mirror on two ad devices. It's got a ZFS root file system. >> >> If you are fairly sure about your devices you can: >> >> 1. Remove second disk from pool or create another pool on top of it. >> >> 2. Recreate all FS structure on the second disk. You can dump al your FS with something like: >> > > Great. Thanks for that. > > Have you got a hint as to how I can get access to the root file system? It's currently set to have a legacy mount point. Which means that when I import the pool: > > # zfs import -o readonly=on -o altroot=/tmp/zfs -f poolname > > the root filesystem is missing. Then if I try and set the mount point: > > #zfs set mountpoint=/tmp/zfs2 poolname > > it just sits there; probably because the command is blocking on the R/O pool, or something. > > How do I temporarily remount the root filesystem so that I can get access to the files? mount -t zfs Personally when I need to work with such pools I first import the pool with -N (nomount) option, then I mount root fs by hand and after that goes `zfs mount -a` which handles everything else. -- Sphinx of black quartz, judge my vow.