From owner-freebsd-fs@FreeBSD.ORG Sun Jun 24 15:28:15 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF29016A46B for ; Sun, 24 Jun 2007 15:28:15 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9776913C45D for ; Sun, 24 Jun 2007 15:28:15 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1I2Trw-0001Yp-A2 for freebsd-fs@freebsd.org; Sun, 24 Jun 2007 17:19:16 +0200 Received: from 89-172-47-11.adsl.net.t-com.hr ([89.172.47.11]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 24 Jun 2007 17:19:16 +0200 Received: from ivoras by 89-172-47-11.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 24 Jun 2007 17:19:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Sun, 24 Jun 2007 17:08:18 +0200 Lines: 33 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEA281A7446E3C0361D3F4715" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-47-11.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) X-Enigmail-Version: 0.94.3.0 Sender: news Cc: freebsd-current@freebsd.org Subject: unionfs and tmpfs? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2007 15:28:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEA281A7446E3C0361D3F4715 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi I'm having trouble mounting tmpfs with unionfs above a read-only file system (cd9660). In my case, /tmp is a tmpfs and I'm doing: # mount_unionfs /tmp /etc mount_unionfs: /etc : Operation not supported. It works if, for example, /tmp is a UFS mounted on a memory device. Is this intentional? --------------enigEA281A7446E3C0361D3F4715 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGfojoldnAQVacBcgRAuLlAKD6gkV0a16O+lnXVuKlFcHJ+IYJdQCg37tB OBb3aJT3fOIONopdnseHvIc= =o1Q7 -----END PGP SIGNATURE----- --------------enigEA281A7446E3C0361D3F4715-- From owner-freebsd-fs@FreeBSD.ORG Tue Jun 26 03:28:14 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8857B16A468 for ; Tue, 26 Jun 2007 03:28:14 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from swin.edu.au (gpo3.cc.swin.edu.au [136.186.1.223]) by mx1.freebsd.org (Postfix) with ESMTP id 09D8113C45E for ; Tue, 26 Jun 2007 03:28:13 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from [136.186.229.95] (lstewart.caia.swin.edu.au [136.186.229.95]) by swin.edu.au (8.13.6.20060614/8.13.1) with ESMTP id l5Q31mf4004122; Tue, 26 Jun 2007 13:01:48 +1000 Message-ID: <468081D6.6010603@room52.net> Date: Tue, 26 Jun 2007 13:02:46 +1000 From: Lawrence Stewart User-Agent: Thunderbird 1.5.0.9 (X11/20070123) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.1.9 X-Spam-Checker-Version: SpamAssassin 3.1.9 (2007-02-13) on gpo3.cc.swin.edu.au Cc: James Healy Subject: Writing a plain text file to disk from kernel space [FYI] X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 03:28:14 -0000 Hi all, As part of a project I've been involved with, we've released some code and a report that might be of interest to people on this list. One of our problems was figuring out how to write to a file directly from kernel space (details archived here: http://lists.freebsd.org/pipermail/freebsd-hackers/2007-May/020544.html). It seems to be a problem a few people have come up against, but we didn't manage to find any obvious answers at the time. We've made a prototype module (named filewriter) available that specifically demonstrates file writing from within the kernel. It should hopefully provide a useful reference implementation for anyone wanting to do this in the future. We've also made a technical report available that documents what we learnt whilst transitioning from noob kernel hackers to guys that have a (partial) clue. The report is certainly a useful reference for us and people working at our research centre. We hope it will also be a useful reference for the community to point people at who are new to kernel hacking. The report's title is "An Introduction to FreeBSD 6 Kernel Hacking" and has been released as Centre for Advanced Internet Architectures Technical Report 070622A. The code distributions and technical report can be grabbed from http://caia.swin.edu.au/urp/newtcp/ under the "Tools" and "Papers" sections respectively. If you find a use for the code or any bugs in the code/documentation, we'd be very happy to hear from you. Cheers, Lawrence From owner-freebsd-fs@FreeBSD.ORG Tue Jun 26 05:03:59 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C1F9816A41F for ; Tue, 26 Jun 2007 05:03:59 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8161213C4AD for ; Tue, 26 Jun 2007 05:03:59 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2277674pyb for ; Mon, 25 Jun 2007 22:03:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=I4vjMHOP3yUE1KYkHwyYF5gk4QdEuyxT2d3msL9LqISL/8O6UKyHWWzYiF9ZfqKl1xqNwwYUm0EVAQHWm6AzvTiHRHlc6O9AEBEohuH2kygeU4242q71+sgTrRW5ktsaxEBcCgyHQo93Zf+4Szf/cgjjzesbVWtsLmzp8huajJs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=BqSI+JkPzIUJ4+ef8k485LLf4Qt61W/CLb0m7XKZ8EvF8pNPuhyEF5YWw4KmlYpFeGD3DOlD4QTpHw768FTpNzuHmFIGWzQZrpHjwT58OYoX7G9w8Nxt95a615f6VYbPB++I/j0pvGxyR21BK1hugH9cC4DLuLMCLC1+qFNlWAM= Received: by 10.35.83.20 with SMTP id k20mr3670918pyl.1182834238816; Mon, 25 Jun 2007 22:03:58 -0700 (PDT) Received: by 10.35.81.5 with HTTP; Mon, 25 Jun 2007 22:03:58 -0700 (PDT) Message-ID: Date: Tue, 26 Jun 2007 13:03:58 +0800 From: "Howard Su" To: fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: old code cleanup?? related to mnt_maxsymlinklen X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2007 05:03:59 -0000 When I read ufs code, i found there are many places checking vp->v_mount->mnt_maxsymlinklen >0. Seems it is for back compactiblity. I am wondering if we can start to cleanup these stuffs. Some comments give the intention that the code is pretty old. /* 4.4 format directories support whiteout operations */ if (dvp->v_mount->mnt_maxsymlinklen > 0) /* true if old FS format...*/ #define OFSFMT(vp) ((vp)->v_mount->mnt_maxsymlinklen <= 0) -- -Howard From owner-freebsd-fs@FreeBSD.ORG Wed Jun 27 11:15:37 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7E6F16A421 for ; Wed, 27 Jun 2007 11:15:37 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id 825F413C458 for ; Wed, 27 Jun 2007 11:15:37 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from imac.housenet.jrv (iMac.housenet.jrv [192.168.3.150]) by mail.jrv.org (8.14.1/8.13.1) with ESMTP id l5RAcLwh024870 for ; Wed, 27 Jun 2007 05:38:21 -0500 (CDT) (envelope-from james-freebsd-fs2@jrv.org) DKIM-Signature: v=0.5; a=rsa-sha256; c=simple/simple; d=jrv.org; s=enigma; t=1182940701; bh=ZD2AFBxaogVkFNy0IEsNDP2J2Y7vBvsUFljQ1rRH55A=; h=DomainKey-Signature: Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: Content-Type:Content-Transfer-Encoding; b=oKEZ/RbS084KeF+YmB1ZKqGl oOasqRV6tAWSBWePoHasP8+eSW5m2EUwui9XTH9V/cD1de4TF7rtzzj3JSL7F58TyqO IfhgyNUU0wW76ZjaGOIVUehYuowppipWPcqDS/tFCisBmwF8ZHdcMPLTMS46bT+Fnwg 9VxGedfBqwNhA= DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: content-type:content-transfer-encoding; b=vNgTNDB+BVfExiW6PM7ZLVpkhet0BmDX0KS7dLdFB9QNTpq5mZBnsTT8bOd4vuq53 AIoRv0jZ7emMl4PJJHQPtdRX0aQkHn9FzBlFT1IFruQfkqvJUJGRBOCqBLaq8IRjhyM xfaft/cumlyaCVM2AducoIu7hg+Ap4Y3Hk7JFII= Message-ID: <46823E1D.8060403@jrv.org> Date: Wed, 27 Jun 2007 05:38:21 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: ZFS - how to recover pool after power loss? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 11:15:37 -0000 What is the right way to recover a pool after a power loss? Neither "zpool import pool" nor "zpool import -f pool" seem to work for me: I get a "no such pool available" error. What *does* seem to work is to destroy the pool, then import the destroyed pool. The setup is a pool with a single vdev, a raidz of five USB disks. FreeBSD i386, the 7.0-CURRENT-200706-i386-disc1.iso image using that kernel. # zpool import no pools available to import # zpool import pool cannot import 'pool': no such pool available # zpool import -f no pools available to import # zpool import -f pool cannot import 'pool': no such pool available # zpool destroy pool # zpool import -D -f pool # From owner-freebsd-fs@FreeBSD.ORG Wed Jun 27 16:14:35 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 36D5916A468 for ; Wed, 27 Jun 2007 16:14:35 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id EB98613C45D for ; Wed, 27 Jun 2007 16:14:34 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so443585pyb for ; Wed, 27 Jun 2007 09:14:34 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:mime-version:content-type; b=Gu+/vb1g/h5u+VyvaTfZT6uWHBWv6IDbxMGdkkDTIh8PkM/NVPWb2v8R85Y+6NM3f7X7FpYsQIRa+uLYBuytGwdEuJK/jecAbPgpGL3gC2Fb+zr4zPSDxJE2jNcsWBwRCuQUR9CqyPFuWCEDNrySsj5elIsHTUW9xqAXLtGru4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=BxGpqe6IA0tLz2PWjgwhx/yH/90jACpEd77q/4JSpGMxc8QEkcBssAf7IbJIuhONhB4VtNxZl4bkfnb5ddvSMa1oN7y1aCjlaZkfaAeoCQRX/0muT6Fqfv9vxyuZotoVL7Dm/clApOa+xfgs/4no7l/HjCObzLqqq0iRf30Y8GA= Received: by 10.35.69.11 with SMTP id w11mr1197975pyk.1182960874273; Wed, 27 Jun 2007 09:14:34 -0700 (PDT) Received: by 10.35.78.11 with HTTP; Wed, 27 Jun 2007 09:14:34 -0700 (PDT) Message-ID: Date: Thu, 28 Jun 2007 00:14:34 +0800 From: "Howard Su" To: fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: danchi@freebsd.org Subject: unionfs requirement for tmpfs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 16:14:35 -0000 Hi All, I am working on tmpfs to make it support unionfs. I think I understand the theory of the unionfs. However I want someone can give me some info regarding the implementation details, like ISWHITEOUT, DOWHITEOUT op. As far as I know, a fs can be used as upper level and lower level fs of a unionfs. The requirement should be different: 1. As a upper level (which will be changed. I am more interested to make tmpfs support this) what is the requirement? So far, based on my code reading on ufs/unionfs, I need implement VOP_WHITEOUT with three OPs: LOOKUP, DELETE, CREATE. what' the expctation of input and output, the code reading can not give me a clear answer. ufs use some hacking way to call into ufs code itself to make the logic unclear to me. 2. As a lower level fs. what's the requirement? I have no idea totally. Share me whatever you know, please. -- -Howard From owner-freebsd-fs@FreeBSD.ORG Wed Jun 27 18:36:45 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7966D16A468 for ; Wed, 27 Jun 2007 18:36:45 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id 4A6D413C457 for ; Wed, 27 Jun 2007 18:36:45 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 0 with SMTP; 27 Jun 2007 18:10:03 -0000 Date: Wed, 27 Jun 2007 21:10:07 +0300 From: Nikolay Pavlov To: Howard Su Message-ID: <20070627181007.GA85316@zone3000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-fs@freebsd.org Subject: tmpfs for /tmp X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 18:36:45 -0000 Hello. I am testing tmpfs on recent current and found one issue. I have this record on fstab: tmpfs /tmp tmpfs rw 0 0 However every time after mount it overwrites /tmp permissions from 777 to 755. Is there any workaround for this? -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-fs@FreeBSD.ORG Wed Jun 27 23:58:09 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AA96716A41F for ; Wed, 27 Jun 2007 23:58:09 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id 619DE13C46A for ; Wed, 27 Jun 2007 23:58:09 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so732433pyb for ; Wed, 27 Jun 2007 16:58:08 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=gqTtdQ2xrLVuAf8tZJgMLeHTxXWBsHmzxvhLyLSbCb36PQH7BxjcycpOYX19L8LsgpuWq4LWGLU9EUGgQ+19OWkf6fy/X2zAxdv0U/3e3N+hC/HgqyJqK6bh1pu5F/KPLrLi0na5EAo07whe8i7axP2/Rmy1S32KOFQvJmwf3fI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ahun/qeWr+R4DnoEfMtnrbFTH0/lUIPlJab+gBfFJmhneJ5FJwZus8znC0V/KhYC2ZHw/cTd453EIJM8BDJH5u/+S7b85M+2T+xmRPRzPrIp9xFLz6Gq0/HbezWM4Cc4F5en/5iDQxUJJtjNWzTF+FLzp6eXEaNwTcBPtOtWIII= Received: by 10.35.71.1 with SMTP id y1mr1841675pyk.1182987141356; Wed, 27 Jun 2007 16:32:21 -0700 (PDT) Received: by 10.35.78.11 with HTTP; Wed, 27 Jun 2007 16:32:11 -0700 (PDT) Message-ID: Date: Thu, 28 Jun 2007 07:32:11 +0800 From: "Howard Su" To: "Nikolay Pavlov" In-Reply-To: <20070627181007.GA85316@zone3000.net> MIME-Version: 1.0 References: <20070627181007.GA85316@zone3000.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: tmpfs for /tmp X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jun 2007 23:58:09 -0000 trytmpfs /tmp tmpfs rw,mode=777 0 0 On 6/28/07, Nikolay Pavlov wrote: > > Hello. I am testing tmpfs on recent current and found one issue. > I have this record on fstab: > tmpfs /tmp tmpfs rw 0 0 > > However every time after mount it overwrites /tmp permissions from 777 to > 755. Is there any workaround for this? > > -- > ====================================================================== > - Best regards, Nikolay Pavlov. <<<----------------------------------- > ====================================================================== > > -- -Howard From owner-freebsd-fs@FreeBSD.ORG Thu Jun 28 12:44:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FB7716A400 for ; Thu, 28 Jun 2007 12:44:41 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 4364513C4B0 for ; Thu, 28 Jun 2007 12:44:38 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id A71C245CD9; Thu, 28 Jun 2007 14:44:36 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 81449487F0; Thu, 28 Jun 2007 14:44:32 +0200 (CEST) Date: Thu, 28 Jun 2007 14:44:30 +0200 From: Pawel Jakub Dawidek To: "James R. Van Artsdalen" Message-ID: <20070628124430.GB9381@garage.freebsd.pl> References: <46823E1D.8060403@jrv.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UHN/qo2QbUvPLonB" Content-Disposition: inline In-Reply-To: <46823E1D.8060403@jrv.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS - how to recover pool after power loss? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 12:44:41 -0000 --UHN/qo2QbUvPLonB Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 27, 2007 at 05:38:21AM -0500, James R. Van Artsdalen wrote: > What is the right way to recover a pool after a power loss? >=20 > Neither "zpool import pool" nor "zpool import -f pool" seem to work for > me: I get a "no such pool available" error. > What *does* seem to work is to destroy the pool, then import the > destroyed pool. >=20 > The setup is a pool with a single vdev, a raidz of five USB disks.=20 > FreeBSD i386, the 7.0-CURRENT-200706-i386-disc1.iso image using that kern= el. >=20 > # zpool import > no pools available to import > # zpool import pool > cannot import 'pool': no such pool available > # zpool import -f > no pools available to import > # zpool import -f pool > cannot import 'pool': no such pool available > # zpool destroy pool > # zpool import -D -f pool Your pool is already imported after power failure. Try 'zpool status'. In other words, pool are imported automatically after power failures, but file systems and ZVOLs are not, you need to use rc.d/zfs script or do it manually: # zfs mount -a # zfs volinit --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --UHN/qo2QbUvPLonB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGg60uForvXbEpPzQRApMUAJsGckTRP+m+IIwVUZMm1IqdbQjZgwCgnNWr bDroKoGExAfuweaiMOzuhas= =jUlv -----END PGP SIGNATURE----- --UHN/qo2QbUvPLonB-- From owner-freebsd-fs@FreeBSD.ORG Thu Jun 28 14:06:18 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B0ED16A400 for ; Thu, 28 Jun 2007 14:06:18 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from mail.jrv.org (adsl-70-243-84-13.dsl.austtx.swbell.net [70.243.84.13]) by mx1.freebsd.org (Postfix) with ESMTP id 2A15113C448 for ; Thu, 28 Jun 2007 14:06:17 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from imac.housenet.jrv (iMac.housenet.jrv [192.168.3.150]) by mail.jrv.org (8.14.1/8.13.1) with ESMTP id l5SE6GXk087067; Thu, 28 Jun 2007 09:06:16 -0500 (CDT) (envelope-from james-freebsd-fs2@jrv.org) DKIM-Signature: v=0.5; a=rsa-sha256; c=simple/simple; d=jrv.org; s=enigma; t=1183039576; bh=BJBEq0GvZBEBvxjiiq/kEzNR9Mu/zhsvBvDOfvvuNeg=; h=DomainKey-Signature: Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=I d5TtxOocC4oAPoYs6rbqWWcT51wuUnd0TuZ6V/JNRQBfTg9Z7GkTivbG9VcDk+rNkAZ xQ5/JETiwM09ejt3vcAYLYaAJixhSfp6eaY0AkRbSIDWV49OSeLYGiQrFoatDrTQY9t Q/fJJrC3/MPpHQ+7G/RiqSnTIkNsC4ge+u1A= DomainKey-Signature: a=rsa-sha1; s=enigma; d=jrv.org; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:cc:subject: references:in-reply-to:content-type:content-transfer-encoding; b=W0cJJoqbZ+mZsH//zqjmrN3cRw1bcAQskEweHgZ+MgwVwJziHitpbHuiXntyPnBUZ mWE+ON/DGlp5I5Y5cly5l1Oh6IolISS1sIaxszT9ikBEUkJWNDeGgN3XvUQwrUmtlCk Lb+9Fi+9Z7wfNcH+SRYb18RWorIXN1CFpLFf5+I= Message-ID: <4683C058.40507@jrv.org> Date: Thu, 28 Jun 2007 09:06:16 -0500 From: "James R. Van Artsdalen" User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <46823E1D.8060403@jrv.org> <20070628124430.GB9381@garage.freebsd.pl> In-Reply-To: <20070628124430.GB9381@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS - how to recover pool after power loss? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2007 14:06:18 -0000 Pawel Jakub Dawidek wrote: > Your pool is already imported after power failure. Try 'zpool status'. > In other words, pool are imported automatically after power failures, > but file systems and ZVOLs are not, you need to use rc.d/zfs script or > do it manually: > > # zfs mount -a > # zfs volinit > > This pool was created with the -R option which I understand means it won't be automatically imported. I get this result after booting # zpool status no pools available #