From owner-freebsd-fs@FreeBSD.ORG Sun Dec 19 02:00:06 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A27CC1065672; Sun, 19 Dec 2010 02:00:06 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 434BD8FC0C; Sun, 19 Dec 2010 02:00:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAHf1DE2DaFvO/2dsb2JhbACDZKFEqk2PSIRWdASEZYYc X-IronPort-AV: E=Sophos;i="4.60,195,1291611600"; d="scan'208";a="104660254" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 18 Dec 2010 21:00:05 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 67959B3F40; Sat, 18 Dec 2010 21:00:05 -0500 (EST) Date: Sat, 18 Dec 2010 21:00:05 -0500 (EST) From: Rick Macklem To: Attila Nagy Message-ID: <2015693782.1796244.1292724005362.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <4C614A7D.8030509@fsn.hu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1796243_680256509.1292724005361" X-Originating-IP: [174.114.46.215] X-Mailer: Zimbra 6.0.7_GA_2476.RHEL4 (ZimbraWebClient - IE8 (Win)/6.0.7_GA_2473.RHEL4_64) Cc: freebsd-fs@freebsd.org, pjd@freebsd.org Subject: Re: NFS problem: file doesn't appear in file listing, but can be accessed directly 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, 19 Dec 2010 02:00:06 -0000 ------=_Part_1796243_680256509.1292724005361 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit > On 08/08/2010 02:06 AM, Rick Macklem wrote: > >> On 07.08.2010, at 02:35, Rick Macklem wrote: > >> > >> I agree, this must be some kind of server issue then. Still, I > >> wonder > >> why the solaris client didn't show the problem... > >> > >> > > 2 things: > > 1 - the solaris client uses ReaddirPlus and not Readdir RPCs by > > default (I can't remember if that default can be overridden?). > I don't know whether this counts or not, but I've tried with an old > Solaris (x86) 8 (uname says it's Generic_108529-06). > > > ps: I don't recall the previous emails mentioning that the "ls" > > was ok for a solaris client. > > > It was in 4C582968.9000303@fsn.hu: > "I've mounted the share from an old Solaris box, which sees the file." > > This means, when I issue an ls | grep problematic_fname, I can see the > filename. > BTW, this turned out to be incorrect, because I've tested with the > same > (one of the missing) filename. > Doing a find . in the directory on both FreeBSD and Solaris client > shows > some differences. > So what I have now is: both the normal and the experimental NFSD show > the problem on both FreeBSD and Solaris clients (only the missing file > names are different). > > On Solaris there are 78 files missing, on FreeBSD there are 193, I > haven't checked that they are persistent across reboots or not. pjd@ just found a problem which affects both the regular and experimental NFS servers when exporting a ZFS volume. (Basically there is a hack in the servers that is needed for UFS, which breaks serving ZFS. If you look in sys/nfs_serv.c and search for "FreeBSD ufs_readdir" in a comment in nfs_readdir() you can read about it. ZFS doesn't generate monotonically increasing directory offset cookies.) If you were using ZFS for the above, please let me know. Also, if you can still reproduce the problem and are exporting ZFS and not UFS, you could test the attached patch (be forwarned that it will break exporting of UFS!!). And, if you get to test this patch, please let me know how it goes. rick ------=_Part_1796243_680256509.1292724005361 Content-Type: text/x-patch; name=zfsreaddir.patch Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=zfsreaddir.patch LS0tIG5mc3NlcnZlci9uZnNfc2Vydi5jLnNhdgkyMDEwLTEyLTE4IDIwOjU0OjA4LjAwMDAwMDAw MCAtMDUwMAorKysgbmZzc2VydmVyL25mc19zZXJ2LmMJMjAxMC0xMi0xOCAyMDo1NTo0MS4wMDAw MDAwMDAgLTA1MDAKQEAgLTI4OTcsOCArMjg5Nyw3IEBACiAJICogaW5jcmVhc2UuCiAJICovCiAJ d2hpbGUgKGNwb3MgPCBjZW5kICYmIG5jb29raWVzID4gMCAmJgotCQkoZHAtPmRfZmlsZW5vID09 IDAgfHwgZHAtPmRfdHlwZSA9PSBEVF9XSFQgfHwKLQkJICgodV9xdWFkX3QpKCpjb29raWVwKSkg PD0gdG9mZikpIHsKKwkJKGRwLT5kX2ZpbGVubyA9PSAwIHx8IGRwLT5kX3R5cGUgPT0gRFRfV0hU KSkgewogCQljcG9zICs9IGRwLT5kX3JlY2xlbjsKIAkJZHAgPSAoc3RydWN0IGRpcmVudCAqKWNw b3M7CiAJCWNvb2tpZXArKzsKQEAgLTMxNzQsOCArMzE3Myw3IEBACiAJICogaW5jcmVhc2UuCiAJ ICovCiAJd2hpbGUgKGNwb3MgPCBjZW5kICYmIG5jb29raWVzID4gMCAmJgotCQkoZHAtPmRfZmls ZW5vID09IDAgfHwgZHAtPmRfdHlwZSA9PSBEVF9XSFQgfHwKLQkJICgodV9xdWFkX3QpKCpjb29r aWVwKSkgPD0gdG9mZikpIHsKKwkJKGRwLT5kX2ZpbGVubyA9PSAwIHx8IGRwLT5kX3R5cGUgPT0g RFRfV0hUKSkgewogCQljcG9zICs9IGRwLT5kX3JlY2xlbjsKIAkJZHAgPSAoc3RydWN0IGRpcmVu dCAqKWNwb3M7CiAJCWNvb2tpZXArKzsK ------=_Part_1796243_680256509.1292724005361-- From owner-freebsd-fs@FreeBSD.ORG Sun Dec 19 04:04:44 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9718C106564A for ; Sun, 19 Dec 2010 04:04:44 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from zimbra.jrv.org (adsl-70-243-84-11.dsl.austtx.swbell.net [70.243.84.11]) by mx1.freebsd.org (Postfix) with ESMTP id 605358FC0A for ; Sun, 19 Dec 2010 04:04:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.jrv.org (Postfix) with ESMTP id 915B716A055 for ; Sat, 18 Dec 2010 21:48:39 -0600 (CST) X-Virus-Scanned: amavisd-new at zimbra.housenet.jrv Received: from zimbra.jrv.org ([127.0.0.1]) by localhost (zimbra.housenet.jrv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vKkpur5JeIRT for ; Sat, 18 Dec 2010 21:48:38 -0600 (CST) Received: from [10.0.2.15] (adsl-99-66-60-249.dsl.aus2tx.sbcglobal.net [99.66.60.249]) by zimbra.jrv.org (Postfix) with ESMTPSA id CA94916A046 for ; Sat, 18 Dec 2010 21:48:37 -0600 (CST) Message-ID: <4D0D8095.6000106@jrv.org> Date: Sat, 18 Dec 2010 21:48:37 -0600 From: "James R. Van Artsdalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <4D0D156B.1070402@jrv.org> In-Reply-To: <4D0D156B.1070402@jrv.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: ZFS recovery after power failure 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, 19 Dec 2010 04:04:44 -0000 On 12/18/2010 2:11 PM, James R. Van Artsdalen wrote: > I do know how to recover pools. But I do want to know how it failed. Er, I meant to say I do NOT know how to recover pools. Sergey's failure doesn't fit any pattern I am familiar with. Loss of power should not have been harmful. Perhaps 3ware "cheats" and returns success to SYNC before the disk actually completes the command? From owner-freebsd-fs@FreeBSD.ORG Sun Dec 19 05:41:43 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF340106564A for ; Sun, 19 Dec 2010 05:41:43 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8436D8FC08 for ; Sun, 19 Dec 2010 05:41:43 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1PUC1e-0006N7-46; Sun, 19 Dec 2010 00:41:42 -0500 Date: Sun, 19 Dec 2010 00:41:42 -0500 From: Gary Palmer To: "James R. Van Artsdalen" Message-ID: <20101219054142.GC70444@in-addr.com> References: <4D0D156B.1070402@jrv.org> <4D0D8095.6000106@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D0D8095.6000106@jrv.org> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS recovery after power failure 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, 19 Dec 2010 05:41:43 -0000 On Sat, Dec 18, 2010 at 09:48:37PM -0600, James R. Van Artsdalen wrote: > On 12/18/2010 2:11 PM, James R. Van Artsdalen wrote: > > I do know how to recover pools. But I do want to know how it failed. > > Er, I meant to say I do NOT know how to recover pools. > > Sergey's failure doesn't fit any pattern I am familiar with. Loss of > power should not have been harmful. > > Perhaps 3ware "cheats" and returns success to SYNC before the disk > actually completes the command? 3ware controllers can be configured with write-back cache even without a battery backup, which will almost certainly mean loss of data if the power is pulled. From owner-freebsd-fs@FreeBSD.ORG Sun Dec 19 10:58:29 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6875106566B for ; Sun, 19 Dec 2010 10:58:28 +0000 (UTC) (envelope-from srg.gavrilov@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9CC4D8FC0C for ; Sun, 19 Dec 2010 10:58:28 +0000 (UTC) Received: by iwn39 with SMTP id 39so2258790iwn.13 for ; Sun, 19 Dec 2010 02:58:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=nmlUvEZhEB6Ke602b3gtg9O5nnYoxklZF8i1iZbAqC0=; b=n8QiAo4MdgXOVWSww0t7QNS1KpFiGYNn3qO13Ja4cxBvZy6bbAU2PaRuKf2r8OMi8k xQlBrexYayvn+2aNeshQWzFBwWp2Nm+Hda7TLmSaWvs27Jkj9r6YqTJEeShiZyChHZsi +mKvDN0ZJPj5KWUouUABJevz5uDY3rlNiS6FU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=QbE/HNwFyrOu42euKluTqUJz5WQet9Au/AxkVM9exfvpk1vvKZixrQL7hXn98gRKjw 9ibN2ucpJYHsFW+TJiaW5nyinwvvBcDmQntQeBlfyUhMft4dFGt9P39nv3bmC2Etc5Wx pXCbCiaB/GLPPrWe91cczqkx66CY/AGkanlPQ= MIME-Version: 1.0 Received: by 10.42.173.196 with SMTP id s4mr2947265icz.70.1292756306760; Sun, 19 Dec 2010 02:58:26 -0800 (PST) Received: by 10.42.150.65 with HTTP; Sun, 19 Dec 2010 02:58:26 -0800 (PST) In-Reply-To: <20101219054142.GC70444@in-addr.com> References: <4D0D156B.1070402@jrv.org> <4D0D8095.6000106@jrv.org> <20101219054142.GC70444@in-addr.com> Date: Sun, 19 Dec 2010 13:58:26 +0300 Message-ID: From: Sergey Gavrilov To: Gary Palmer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS recovery after power failure 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, 19 Dec 2010 10:58:29 -0000 Yes, you're right Gary. That's what it was. 2010/12/19 Gary Palmer > On Sat, Dec 18, 2010 at 09:48:37PM -0600, James R. Van Artsdalen wrote: > > On 12/18/2010 2:11 PM, James R. Van Artsdalen wrote: > > > I do know how to recover pools. But I do want to know how it failed. > > > > Er, I meant to say I do NOT know how to recover pools. > > > > Sergey's failure doesn't fit any pattern I am familiar with. Loss of > > power should not have been harmful. > > > > Perhaps 3ware "cheats" and returns success to SYNC before the disk > > actually completes the command? > > 3ware controllers can be configured with write-back cache even without > a battery backup, which will almost certainly mean loss of > data if the power is pulled. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- Best regards, Sergey Gavrilov From owner-freebsd-fs@FreeBSD.ORG Sun Dec 19 13:00:28 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B4FD106567A for ; Sun, 19 Dec 2010 13:00:28 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id C84068FC14 for ; Sun, 19 Dec 2010 13:00:27 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 5216E45CA6; Sun, 19 Dec 2010 13:30:46 +0100 (CET) Received: from localhost (89-73-192-49.dynamic.chello.pl [89.73.192.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 6582945C8A; Sun, 19 Dec 2010 13:30:40 +0100 (CET) Date: Sun, 19 Dec 2010 13:30:29 +0100 From: Pawel Jakub Dawidek To: Sergey Gavrilov Message-ID: <20101219123029.GM2127@garage.freebsd.pl> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ELVYuRnMxQ5nnKRy" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS recovery after power failure 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, 19 Dec 2010 13:00:28 -0000 --ELVYuRnMxQ5nnKRy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 18, 2010 at 11:21:52AM +0300, Sergey Gavrilov wrote: > zpool import -F pool2 ok, but > zpool status -xv > pool: pool2 > state: FAULTED > status: The pool metadata is corrupted and the pool cannot be opened. > action: Destroy and re-create the pool from a backup source. > see: http://www.sun.com/msg/ZFS-8000-72 > scrub: none requested > config: >=20 > NAME STATE READ WRITE CKSUM > pool2 FAULTED 0 0 1 corrupted data > raidz2 ONLINE 0 0 6 > da9 ONLINE 0 0 0 > da10 ONLINE 0 0 0 > da11 ONLINE 0 0 0 > da12 ONLINE 0 0 0 > da13 ONLINE 0 0 0 > da14 ONLINE 0 0 0 > da15 ONLINE 0 0 0 > da16 ONLINE 0 0 0 >=20 > zpool clear pool2 > cannot clear errors for pool2: I/O error >=20 > Is there any way to recovery data or portion of data at least. Could you provide output of: # apply "zdb -l /dev/da%1 | egrep '(^LABEL|txg=3D|)'" `jot 8 9` --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ELVYuRnMxQ5nnKRy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk0N+uUACgkQForvXbEpPzSpvwCffacEvJXgsGS8igZ0Q497e5ry YAEAoPCrPyUY9uIjFIbwSb3KtoKSg+fM =AixM -----END PGP SIGNATURE----- --ELVYuRnMxQ5nnKRy-- From owner-freebsd-fs@FreeBSD.ORG Sun Dec 19 15:13:40 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9FC17106566C; Sun, 19 Dec 2010 15:13:40 +0000 (UTC) (envelope-from srg.gavrilov@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 56EC58FC0C; Sun, 19 Dec 2010 15:13:40 +0000 (UTC) Received: by iwn39 with SMTP id 39so2382359iwn.13 for ; Sun, 19 Dec 2010 07:13:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=txtRQvGReQIMdAId0RbMeGqPTnabAU2kAOJeZTkXTFk=; b=Uk5VvCP364/Xl+QK1RDCD504XPwi8/+gEM7wkSCIJi42AA/BM9LYhYm0hgbJd4QwGu 2/j1T8/7AeK+vjM9sIuI9J/vgM8UlTei5XavzD51PMdxMsWrztqB2XAQxIGv+2gYzWQ8 9X57JZdfrIr1XX+dYXnbqeezxOvZQEZBjllpc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=fF88J4ic4cM1hGVX/Zu8ixK/Y7XfyAWHVrihqe5rJaBZ3y/U18YuYhkW8ep+io5bml RAchwaWl+2i/9f4wmmgoVDq4zgSrtYEJaKdZSVDSas138clUVCii7iD8dtiNCGrGMtTB lbCdWkzr6qpOVhI0PpDHFARde/By2Wahfd/c0= MIME-Version: 1.0 Received: by 10.42.178.69 with SMTP id bl5mr3091655icb.338.1292771619596; Sun, 19 Dec 2010 07:13:39 -0800 (PST) Received: by 10.42.150.65 with HTTP; Sun, 19 Dec 2010 07:13:39 -0800 (PST) In-Reply-To: <20101219123029.GM2127@garage.freebsd.pl> References: <20101219123029.GM2127@garage.freebsd.pl> Date: Sun, 19 Dec 2010 18:13:39 +0300 Message-ID: From: Sergey Gavrilov To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS recovery after power failure 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, 19 Dec 2010 15:13:40 -0000 I've destroyed 2 latest uberblocks and imported pool. It's ok now. Your command don't work for me as is, but all tgx nubmers of all labels are the same and equal 666999 now. Think it's already useless information. So I saved those uberblocks. I can provide them if you need. 2010/12/19 Pawel Jakub Dawidek > On Sat, Dec 18, 2010 at 11:21:52AM +0300, Sergey Gavrilov wrote: > > zpool import -F pool2 ok, but > > zpool status -xv > > pool: pool2 > > state: FAULTED > > status: The pool metadata is corrupted and the pool cannot be opened. > > action: Destroy and re-create the pool from a backup source. > > see: http://www.sun.com/msg/ZFS-8000-72 > > scrub: none requested > > config: > > > > NAME STATE READ WRITE CKSUM > > pool2 FAULTED 0 0 1 corrupted data > > raidz2 ONLINE 0 0 6 > > da9 ONLINE 0 0 0 > > da10 ONLINE 0 0 0 > > da11 ONLINE 0 0 0 > > da12 ONLINE 0 0 0 > > da13 ONLINE 0 0 0 > > da14 ONLINE 0 0 0 > > da15 ONLINE 0 0 0 > > da16 ONLINE 0 0 0 > > > > zpool clear pool2 > > cannot clear errors for pool2: I/O error > > > > Is there any way to recovery data or portion of data at least. > > Could you provide output of: > > # apply "zdb -l /dev/da%1 | egrep '(^LABEL|txg=|)'" `jot 8 9` > > -- > Pawel Jakub Dawidek http://www.wheelsystems.com > pjd@FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! > -- Best regards, Sergey Gavrilov From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 00:25:10 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BC7F106566C for ; Mon, 20 Dec 2010 00:25:10 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (DMZ-MAILSEC-SCANNER-7.MIT.EDU [18.7.68.36]) by mx1.freebsd.org (Postfix) with ESMTP id C05658FC14 for ; Mon, 20 Dec 2010 00:25:09 +0000 (UTC) X-AuditID: 12074424-b7b0bae000000a05-04-4d0e9edf6da0 Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-7.mit.edu (Symantec Brightmail Gateway) with SMTP id AF.22.02565.FDE9E0D4; Sun, 19 Dec 2010 19:10:07 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id oBK0A7t6012645 for ; Sun, 19 Dec 2010 19:10:07 -0500 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id oBK0A500010268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 19 Dec 2010 19:10:06 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id oBK0A4ns008561; Sun, 19 Dec 2010 19:10:04 -0500 (EST) Date: Sun, 19 Dec 2010 19:10:04 -0500 (EST) From: Benjamin Kaduk To: freebsd-fs@freebsd.org Message-ID: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: AAAAAA== Subject: debugging process in bovlbx state 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: Mon, 20 Dec 2010 00:25:10 -0000 Hi all, I'm working on bringing the out-of-tree OpenAFS network filesystem up-to-date for FreeBSD 7.3-RELEASE, and I think I need some help to fix this bug. I should preface my discourse with the fact that there is a whole slow of lock order reversals that I haven't even tried to track down, but I do not believe that this hang is deadlock since 'show alllocks' in DDB does not show anything that seems interesting. Any pointers for things to look at would be appreciated; more details of the failing case below. In order to get the afs kernel module to load, I needed to tweak a few lines of code in getpages(), as I had previously cribbed a bunch of changes/updates from the experimental NFS client while getting AFS to work on current freebsd. In particular, vm_page_set_valid is not present in 7.3, so I am currently running with: --- a/src/afs/FBSD/osi_vnodeops.c +++ b/src/afs/FBSD/osi_vnodeops.c @@ -890,12 +890,8 @@ afs_vop_getpages(struct vop_getpages_args *ap) * Read operation filled a partial page. */ m->valid = 0; - vm_page_set_valid(m, 0, size - toff); -#ifndef AFS_FBSD80_ENV - vm_page_undirty(m); -#else + vm_page_set_validclean(m, 0, size - toff); KASSERT(m->dirty == 0, ("afs_getpages: page %p is dirty", m)); -#endif } But my knowledge of vm_page_* is approximately nil, so there's no reason to think everything was correct even before that patch. Anyway, my test case is running libarchive's configure script with source and destination directories in (different places in) AFS. It only gets twenty lines in, ending with: checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... ^Tload: 0.04 cmd: cp 1250 [bovlbx] 0.00u 0.00 procstat -kk reports: mega-man# procstat -kk 1250 PID TID COMM TDNAME KSTACK 1250 100060 cp - mi_switch+0x233 sleepq_switch+0xe9 sleepq_wait+0x44 _sleep+0x3a0 vm_object_pip_wait+0x4e bufobj_invalbuf+0x10e afs_GetVCache+0x2f7 The call to vinvalbuf in afs_GetVCache is here: 1646 iheldthelock = VOP_ISLOCKED(vp, curthread); 1647 if (!iheldthelock) 1648 vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, curthread); 1649 AFS_GUNLOCK(); 1650 vinvalbuf(vp, V_SAVE, curthread, PINOD, 0); 1651 AFS_GLOCK(); 1652 if (!iheldthelock) 1653 VOP_UNLOCK(vp, LK_EXCLUSIVE, curthread); Which is not very enlightening. I kind of suspect that some flags on the bufobj were erroneously set elsewhere and it is only now popping up. afs_GetVCache is in this source file: http://git.openafs.org/?p=openafs.git;a=blob;f=src/afs/afs_vcache.c;h=26ed2c2be271048509425583f0cc2de6c4166c4b;hb=HEAD and {get,put}pages in this: http://git.openafs.org/?p=openafs.git;a=blob;f=src/afs/FBSD/osi_vnodeops.c;h=7ae6571adb74d69cfe25e3190ade3b22dc8cdab8;hb=HEAD Thanks, Ben Kaduk From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 01:06:11 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 118FA1065679 for ; Mon, 20 Dec 2010 01:06:11 +0000 (UTC) (envelope-from freebsd-fs@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id BBA498FC1A for ; Mon, 20 Dec 2010 01:06:10 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PUUCX-0006MF-Cu for freebsd-fs@freebsd.org; Mon, 20 Dec 2010 02:06:09 +0100 Received: from cpe-188-129-92-161.dynamic.amis.hr ([188.129.92.161]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Dec 2010 02:06:09 +0100 Received: from ivoras by cpe-188-129-92-161.dynamic.amis.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 20 Dec 2010 02:06:09 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-fs@freebsd.org From: Ivan Voras Date: Mon, 20 Dec 2010 02:05:57 +0100 Lines: 5 Message-ID: References: <20101219123029.GM2127@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: cpe-188-129-92-161.dynamic.amis.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101102 Thunderbird/3.1.6 In-Reply-To: Subject: Re: ZFS recovery after power failure 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: Mon, 20 Dec 2010 01:06:11 -0000 On 12/19/10 16:13, Sergey Gavrilov wrote: > I've destroyed 2 latest uberblocks and imported pool. It's ok now. A case for fsck.zfs? :) From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 04:18:21 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 828C0106566C for ; Mon, 20 Dec 2010 04:18:21 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from zimbra.jrv.org (adsl-70-243-84-11.dsl.austtx.swbell.net [70.243.84.11]) by mx1.freebsd.org (Postfix) with ESMTP id 42C5F8FC14 for ; Mon, 20 Dec 2010 04:18:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.jrv.org (Postfix) with ESMTP id 32B4C16A05D; Sun, 19 Dec 2010 22:18:20 -0600 (CST) X-Virus-Scanned: amavisd-new at zimbra.housenet.jrv Received: from zimbra.jrv.org ([127.0.0.1]) by localhost (zimbra.housenet.jrv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cc2g+9nqZDoz; Sun, 19 Dec 2010 22:18:19 -0600 (CST) Received: from [10.0.2.15] (adsl-99-66-60-249.dsl.aus2tx.sbcglobal.net [99.66.60.249]) by zimbra.jrv.org (Postfix) with ESMTPSA id 6D16416A049; Sun, 19 Dec 2010 22:18:19 -0600 (CST) Message-ID: <4D0ED910.5010408@jrv.org> Date: Sun, 19 Dec 2010 22:18:24 -0600 From: "James R. Van Artsdalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Ivan Voras References: <20101219123029.GM2127@garage.freebsd.pl> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS recovery after power failure 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: Mon, 20 Dec 2010 04:18:21 -0000 On 12/19/2010 7:05 PM, Ivan Voras wrote: > On 12/19/10 16:13, Sergey Gavrilov wrote: >> I've destroyed 2 latest uberblocks and imported pool. It's ok now. > > A case for fsck.zfs? :) No. It's random chance that this didn't damage the pool beyond any recovery. Better to spend the effort fixing the problem, which is what Sun did in v28. From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 06:59:24 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BB701065673 for ; Mon, 20 Dec 2010 06:59:24 +0000 (UTC) (envelope-from srg.gavrilov@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B5E018FC17 for ; Mon, 20 Dec 2010 06:59:23 +0000 (UTC) Received: by iyb26 with SMTP id 26so1999674iyb.13 for ; Sun, 19 Dec 2010 22:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=nniVGTXvvJBkWUYMpkOxRBaPR+3ohqX0aEYyP0yqYzU=; b=DKwATZIt6OzamcvK3C9lwNbY8XVODNj2SbVYFyrEA7/nyMgjsk96NES/BCw7YzXAHA mtv6bvs7aUeODGNtf2FDfWQkxzeoCwyfwzMu8IeySXe4DmyrufAZimRHEkLrN0NIKsAw snbh7XnB/XpE0vbTy9/VgEUNPFMBEhwpI0rn0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=TFAqe7l3/g9i8KK/724o8BtsjKzLFFiLI9rmoF2zubqPOqzeV7UuShHUfCHkgHDjxq BjZb7TIDMfMKC97PbhVoKNScILBXJdhgK78I/0Kr7gSkJkCqAyqhC3gyXcljjT8Hvsp4 F2UX1/yhbLAijBXzBBQDw94AVqB/FZG5FDK48= MIME-Version: 1.0 Received: by 10.42.217.129 with SMTP id hm1mr3806751icb.137.1292828362781; Sun, 19 Dec 2010 22:59:22 -0800 (PST) Received: by 10.42.150.65 with HTTP; Sun, 19 Dec 2010 22:59:22 -0800 (PST) In-Reply-To: <4D0ED910.5010408@jrv.org> References: <20101219123029.GM2127@garage.freebsd.pl> <4D0ED910.5010408@jrv.org> Date: Mon, 20 Dec 2010 09:59:22 +0300 Message-ID: From: Sergey Gavrilov To: "James R. Van Artsdalen" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, Ivan Voras Subject: Re: ZFS recovery after power failure 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: Mon, 20 Dec 2010 06:59:24 -0000 Could you tell about why it can damage the pool in more details, please. 2010/12/20 James R. Van Artsdalen > On 12/19/2010 7:05 PM, Ivan Voras wrote: > > On 12/19/10 16:13, Sergey Gavrilov wrote: > >> I've destroyed 2 latest uberblocks and imported pool. It's ok now. > > > > A case for fsck.zfs? :) > > No. It's random chance that this didn't damage the pool beyond any > recovery. Better to spend the effort fixing the problem, which is what > Sun did in v28. > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > -- Best regards, Sergey Gavrilov From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 08:45:12 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CE0E106566C; Mon, 20 Dec 2010 08:45:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 432208FC12; Mon, 20 Dec 2010 08:45:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBK8jC68069095; Mon, 20 Dec 2010 08:45:12 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBK8jC55069091; Mon, 20 Dec 2010 08:45:12 GMT (envelope-from linimon) Date: Mon, 20 Dec 2010 08:45:12 GMT Message-Id: <201012200845.oBK8jC55069091@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/153126: [zfs] vdev failure, zpool=peegel type=vdev.too_small 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: Mon, 20 Dec 2010 08:45:12 -0000 Old Synopsis: ZFS: vdev failure, zpool=peegel type=vdev.too_small New Synopsis: [zfs] vdev failure, zpool=peegel type=vdev.too_small Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 20 08:44:53 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=153126 From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 11:06:56 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89F4E10656EF for ; Mon, 20 Dec 2010 11:06:56 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5C79D8FC16 for ; Mon, 20 Dec 2010 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBKB6uoi024528 for ; Mon, 20 Dec 2010 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBKB6tOQ024526 for freebsd-fs@FreeBSD.org; Mon, 20 Dec 2010 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 20 Dec 2010 11:06:55 GMT Message-Id: <201012201106.oBKB6tOQ024526@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-fs@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-fs@FreeBSD.org 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: Mon, 20 Dec 2010 11:06:56 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o bin/153258 fs [patch][zfs] creating ZVOLs requires `refreservation' s kern/153173 fs [zfs] booting from a gzip-compressed dataset doesn't w o kern/153126 fs [zfs] vdev failure, zpool=peegel type=vdev.too_small o kern/152605 fs [ufs] [panic] handle_workitem_freeblocks: inode 18 blo o kern/152488 fs [tmpfs] [patch] mtime of file updated when only inode o kern/152079 fs [msdosfs] [patch] Small cleanups from the other NetBSD o kern/152022 fs [nfs] nfs service hangs with linux client [regression] o kern/151942 fs [zfs] panic during ls(1) zfs snapshot directory o kern/151905 fs [zfs] page fault under load in /sbin/zfs o kern/151845 fs [smbfs] [patch] smbfs should be upgraded to support Un o bin/151713 fs [patch] Bug in growfs(8) with respect to 32-bit overfl o kern/151648 fs [zfs] disk wait bug o kern/151629 fs [fs] [patch] Skip empty directory entries during name o kern/151330 fs [zfs] will unshare all zfs filesystem after execute a o kern/151326 fs [nfs] nfs exports fail if netgroups contain duplicate o kern/151251 fs [ufs] Can not create files on filesystem with heavy us o kern/151226 fs [zfs] can't delete zfs snapshot o kern/151111 fs [zfs] vnodes leakage during zfs unmount o kern/150796 fs [panic] [suj] [ufs] [softupdates] Panic on portbuild o kern/150503 fs [zfs] ZFS disks are UNAVAIL and corrupted after reboot o kern/150501 fs [zfs] ZFS vdev failure vdev.bad_label on amd64 o kern/150390 fs [zfs] zfs deadlock when arcmsr reports drive faulted o kern/150336 fs [nfs] mountd/nfsd became confused; refused to reload n o kern/150207 fs zpool(1): zpool import -d /dev tries to open weird dev o kern/149208 fs mksnap_ffs(8) hang/deadlock o kern/149173 fs [patch] [zfs] make OpenSolaris installa o kern/149022 fs [hang] File system operations hangs with suspfs state o kern/149015 fs [zfs] [patch] misc fixes for ZFS code to build on Glib o kern/149014 fs [zfs] [patch] declarations in ZFS libraries/utilities o kern/149013 fs [zfs] [patch] make ZFS makefiles use the libraries fro o kern/148504 fs [zfs] ZFS' zpool does not allow replacing drives to be o kern/148490 fs [zfs]: zpool attach - resilver bidirectionally, and re o kern/148368 fs [zfs] ZFS hanging forever on 8.1-PRERELEASE o bin/148296 fs [zfs] [loader] [patch] Very slow probe in /usr/src/sys o kern/148204 fs [nfs] UDP NFS causes overload o kern/148138 fs [zfs] zfs raidz pool commands freeze o kern/147903 fs [zfs] [panic] Kernel panics on faulty zfs device o kern/147881 fs [zfs] [patch] ZFS "sharenfs" doesn't allow different " o kern/147790 fs [zfs] zfs set acl(mode|inherit) fails on existing zfs o kern/147560 fs [zfs] [boot] Booting 8.1-PRERELEASE raidz system take o kern/147420 fs [ufs] [panic] ufs_dirbad, nullfs, jail panic (corrupt o kern/146941 fs [zfs] [panic] Kernel Double Fault - Happens constantly o kern/146786 fs [zfs] zpool import hangs with checksum errors o kern/146708 fs [ufs] [panic] Kernel panic in softdep_disk_write_compl o kern/146528 fs [zfs] Severe memory leak in ZFS on i386 o kern/146502 fs [nfs] FreeBSD 8 NFS Client Connection to Server o kern/146375 fs [nfs] [patch] Typos in macro variables names in sys/fs s kern/145712 fs [zfs] cannot offline two drives in a raidz2 configurat o kern/145411 fs [xfs] [panic] Kernel panics shortly after mounting an o bin/145309 fs bsdlabel: Editing disk label invalidates the whole dev o kern/145272 fs [zfs] [panic] Panic during boot when accessing zfs on o kern/145246 fs [ufs] dirhash in 7.3 gratuitously frees hashes when it o kern/145238 fs [zfs] [panic] kernel panic on zpool clear tank o kern/145229 fs [zfs] Vast differences in ZFS ARC behavior between 8.0 o kern/145189 fs [nfs] nfsd performs abysmally under load o kern/144929 fs [ufs] [lor] vfs_bio.c + ufs_dirhash.c o kern/144458 fs [nfs] [patch] nfsd fails as a kld p kern/144447 fs [zfs] sharenfs fsunshare() & fsshare_main() non functi o kern/144416 fs [panic] Kernel panic on online filesystem optimization s kern/144415 fs [zfs] [panic] kernel panics on boot after zfs crash o kern/144234 fs [zfs] Cannot boot machine with recent gptzfsboot code o kern/143825 fs [nfs] [panic] Kernel panic on NFS client o bin/143572 fs [zfs] zpool(1): [patch] The verbose output from iostat o kern/143345 fs [ext2fs] [patch] extfs minor header cleanups to better o kern/143212 fs [nfs] NFSv4 client strange work ... o kern/143184 fs [zfs] [lor] zfs/bufwait LOR o kern/142924 fs [ext2fs] [patch] Small cleanup for the inode struct in o kern/142914 fs [zfs] ZFS performance degradation over time o kern/142878 fs [zfs] [vfs] lock order reversal o kern/142597 fs [ext2fs] ext2fs does not work on filesystems with real o kern/142489 fs [zfs] [lor] allproc/zfs LOR o kern/142466 fs Update 7.2 -> 8.0 on Raid 1 ends with screwed raid [re o kern/142401 fs [ntfs] [patch] Minor updates to NTFS from NetBSD o kern/142306 fs [zfs] [panic] ZFS drive (from OSX Leopard) causes two o kern/142068 fs [ufs] BSD labels are got deleted spontaneously o kern/141897 fs [msdosfs] [panic] Kernel panic. msdofs: file name leng o kern/141463 fs [nfs] [panic] Frequent kernel panics after upgrade fro o kern/141305 fs [zfs] FreeBSD ZFS+sendfile severe performance issues ( o kern/141091 fs [patch] [nullfs] fix panics with DIAGNOSTIC enabled o kern/141086 fs [nfs] [panic] panic("nfs: bioread, not dir") on FreeBS o kern/141010 fs [zfs] "zfs scrub" fails when backed by files in UFS2 o kern/140888 fs [zfs] boot fail from zfs root while the pool resilveri o kern/140661 fs [zfs] [patch] /boot/loader fails to work on a GPT/ZFS- o kern/140640 fs [zfs] snapshot crash o kern/140134 fs [msdosfs] write and fsck destroy filesystem integrity o kern/140068 fs [smbfs] [patch] smbfs does not allow semicolon in file o kern/139725 fs [zfs] zdb(1) dumps core on i386 when examining zpool c o kern/139715 fs [zfs] vfs.numvnodes leak on busy zfs o bin/139651 fs [nfs] mount(8): read-only remount of NFS volume does n o kern/139597 fs [patch] [tmpfs] tmpfs initializes va_gen but doesn't u o kern/139564 fs [zfs] [panic] 8.0-RC1 - Fatal trap 12 at end of shutdo o kern/139407 fs [smbfs] [panic] smb mount causes system crash if remot o kern/138790 fs [zfs] ZFS ceases caching when mem demand is high o kern/138662 fs [panic] ffs_blkfree: freeing free block o kern/138421 fs [ufs] [patch] remove UFS label limitations o kern/138202 fs mount_msdosfs(1) see only 2Gb o kern/136968 fs [ufs] [lor] ufs/bufwait/ufs (open) o kern/136945 fs [ufs] [lor] filedesc structure/ufs (poll) o kern/136944 fs [ffs] [lor] bufwait/snaplk (fsync) o kern/136873 fs [ntfs] Missing directories/files on NTFS volume o kern/136865 fs [nfs] [patch] NFS exports atomic and on-the-fly atomic o kern/136470 fs [nfs] Cannot mount / in read-only, over NFS o kern/135667 fs [lor] LORs causing ufs filesystem corruption on XEN Do o kern/135546 fs [zfs] zfs.ko module doesn't ignore zpool.cache filenam o kern/135469 fs [ufs] [panic] kernel crash on md operation in ufs_dirb o kern/135050 fs [zfs] ZFS clears/hides disk errors on reboot o kern/134491 fs [zfs] Hot spares are rather cold... o kern/133676 fs [smbfs] [panic] umount -f'ing a vnode-based memory dis o kern/133614 fs [panic] panic: ffs_truncate: read-only filesystem o kern/133174 fs [msdosfs] [patch] msdosfs must support utf-encoded int o kern/132960 fs [ufs] [panic] panic:ffs_blkfree: freeing free frag o kern/132397 fs reboot causes filesystem corruption (failure to sync b o kern/132331 fs [ufs] [lor] LOR ufs and syncer o kern/132237 fs [msdosfs] msdosfs has problems to read MSDOS Floppy o kern/132145 fs [panic] File System Hard Crashes o kern/131441 fs [unionfs] [nullfs] unionfs and/or nullfs not combineab o kern/131360 fs [nfs] poor scaling behavior of the NFS server under lo o kern/131342 fs [nfs] mounting/unmounting of disks causes NFS to fail o bin/131341 fs makefs: error "Bad file descriptor" on the mount poin o kern/130920 fs [msdosfs] cp(1) takes 100% CPU time while copying file o kern/130210 fs [nullfs] Error by check nullfs o kern/129760 fs [nfs] after 'umount -f' of a stale NFS share FreeBSD l o kern/129488 fs [smbfs] Kernel "bug" when using smbfs in smbfs_smb.c: o kern/129231 fs [ufs] [patch] New UFS mount (norandom) option - mostly o kern/129152 fs [panic] non-userfriendly panic when trying to mount(8) o kern/127787 fs [lor] [ufs] Three LORs: vfslock/devfs/vfslock, ufs/vfs o bin/127270 fs fsck_msdosfs(8) may crash if BytesPerSec is zero o kern/127029 fs [panic] mount(8): trying to mount a write protected zi o kern/126287 fs [ufs] [panic] Kernel panics while mounting an UFS file o kern/125895 fs [ffs] [panic] kernel: panic: ffs_blkfree: freeing free s kern/125738 fs [zfs] [request] SHA256 acceleration in ZFS o kern/123939 fs [msdosfs] corrupts new files o kern/122380 fs [ffs] ffs_valloc:dup alloc (Soekris 4801/7.0/USB Flash o bin/122172 fs [fs]: amd(8) automount daemon dies on 6.3-STABLE i386, o bin/121898 fs [nullfs] pwd(1)/getcwd(2) fails with Permission denied o bin/121779 fs [ufs] snapinfo(8) (and related tools?) only work for t o bin/121366 fs [zfs] [patch] Automatic disk scrubbing from periodic(8 o bin/121072 fs [smbfs] mount_smbfs(8) cannot normally convert the cha f kern/120991 fs [panic] [ffs] [snapshot] System crashes when manipulat o kern/120483 fs [ntfs] [patch] NTFS filesystem locking changes o kern/120482 fs [ntfs] [patch] Sync style changes between NetBSD and F o kern/118912 fs [2tb] disk sizing/geometry problem with large array o kern/118713 fs [minidump] [patch] Display media size required for a k o bin/118249 fs [ufs] mv(1): moving a directory changes its mtime o kern/118107 fs [ntfs] [panic] Kernel panic when accessing a file at N o kern/117954 fs [ufs] dirhash on very large directories blocks the mac o bin/117315 fs [smbfs] mount_smbfs(8) and related options can't mount o kern/117314 fs [ntfs] Long-filename only NTFS fs'es cause kernel pani o kern/117158 fs [zfs] zpool scrub causes panic if geli vdevs detach on o bin/116980 fs [msdosfs] [patch] mount_msdosfs(8) resets some flags f o conf/116931 fs lack of fsck_cd9660 prevents mounting iso images with p kern/116608 fs [msdosfs] [patch] msdosfs fails to check mount options o kern/116583 fs [ffs] [hang] System freezes for short time when using o kern/116170 fs [panic] Kernel panic when mounting /tmp o bin/115361 fs [zfs] mount(8) gets into a state where it won't set/un o kern/114955 fs [cd9660] [patch] [request] support for mask,dirmask,ui o kern/114847 fs [ntfs] [patch] [request] dirmask support for NTFS ala o kern/114676 fs [ufs] snapshot creation panics: snapacct_ufs2: bad blo o bin/114468 fs [patch] [request] add -d option to umount(8) to detach o kern/113852 fs [smbfs] smbfs does not properly implement DFS referral o bin/113838 fs [patch] [request] mount(8): add support for relative p o bin/113049 fs [patch] [request] make quot(8) use getopt(3) and show o kern/112658 fs [smbfs] [patch] smbfs and caching problems (resolves b o kern/111843 fs [msdosfs] Long Names of files are incorrectly created o kern/111782 fs [ufs] dump(8) fails horribly for large filesystems s bin/111146 fs [2tb] fsck(8) fails on 6T filesystem o kern/109024 fs [msdosfs] [iconv] mount_msdosfs: msdosfs_iconv: Operat o kern/109010 fs [msdosfs] can't mv directory within fat32 file system o bin/107829 fs [2TB] fdisk(8): invalid boundary checking in fdisk / w o kern/106107 fs [ufs] left-over fsck_snapshot after unfinished backgro o kern/106030 fs [ufs] [panic] panic in ufs from geom when a dead disk o kern/104406 fs [ufs] Processes get stuck in "ufs" state under persist o kern/104133 fs [ext2fs] EXT2FS module corrupts EXT2/3 filesystems o kern/103035 fs [ntfs] Directories in NTFS mounted disc images appear o kern/101324 fs [smbfs] smbfs sometimes not case sensitive when it's s o kern/99290 fs [ntfs] mount_ntfs ignorant of cluster sizes s bin/97498 fs [request] newfs(8) has no option to clear the first 12 o kern/97377 fs [ntfs] [patch] syntax cleanup for ntfs_ihash.c o kern/95222 fs [cd9660] File sections on ISO9660 level 3 CDs ignored o kern/94849 fs [ufs] rename on UFS filesystem is not atomic o bin/94810 fs fsck(8) incorrectly reports 'file system marked clean' o kern/94769 fs [ufs] Multiple file deletions on multi-snapshotted fil o kern/94733 fs [smbfs] smbfs may cause double unlock o bin/94635 fs snapinfo(8)/libufs only works for disk-backed filesyst o kern/93942 fs [vfs] [patch] panic: ufs_dirbad: bad dir (patch from D o kern/92272 fs [ffs] [hang] Filling a filesystem while creating a sna o kern/91134 fs [smbfs] [patch] Preserve access and modification time a kern/90815 fs [smbfs] [patch] SMBFS with character conversions somet o kern/88657 fs [smbfs] windows client hang when browsing a samba shar o kern/88555 fs [panic] ffs_blkfree: freeing free frag on AMD 64 o kern/88266 fs [smbfs] smbfs does not implement UIO_NOCOPY and sendfi o bin/87966 fs [patch] newfs(8): introduce -A flag for newfs to enabl o kern/87859 fs [smbfs] System reboot while umount smbfs. o kern/86587 fs [msdosfs] rm -r /PATH fails with lots of small files o bin/85494 fs fsck_ffs: unchecked use of cg_inosused macro etc. o kern/80088 fs [smbfs] Incorrect file time setting on NTFS mounted vi o bin/74779 fs Background-fsck checks one filesystem twice and omits o kern/73484 fs [ntfs] Kernel panic when doing `ls` from the client si o bin/73019 fs [ufs] fsck_ufs(8) cannot alloc 607016868 bytes for ino o kern/71774 fs [ntfs] NTFS cannot "see" files on a WinXP filesystem o bin/70600 fs fsck(8) throws files away when it can't grow lost+foun o kern/68978 fs [panic] [ufs] crashes with failing hard disk, loose po o kern/65920 fs [nwfs] Mounted Netware filesystem behaves strange o kern/65901 fs [smbfs] [patch] smbfs fails fsx write/truncate-down/tr o kern/61503 fs [smbfs] mount_smbfs does not work as non-root o kern/55617 fs [smbfs] Accessing an nsmb-mounted drive via a smb expo o kern/51685 fs [hang] Unbounded inode allocation causes kernel to loc o kern/51583 fs [nullfs] [patch] allow to work with devices and socket o kern/36566 fs [smbfs] System reboot with dead smb mount and umount o kern/33464 fs [ufs] soft update inconsistencies after system crash o bin/27687 fs fsck(8) wrapper is not properly passing options to fsc o kern/18874 fs [2TB] 32bit NFS servers export wrong negative values t 212 problems total. From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 13:12:33 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 055151065670 for ; Mon, 20 Dec 2010 13:12:33 +0000 (UTC) (envelope-from james-freebsd-fs2@jrv.org) Received: from zimbra.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.freebsd.org (Postfix) with ESMTP id BC5698FC0C for ; Mon, 20 Dec 2010 13:12:32 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.jrv.org (Postfix) with ESMTP id AC01816A049; Mon, 20 Dec 2010 07:12:31 -0600 (CST) X-Virus-Scanned: amavisd-new at zimbra.housenet.jrv Received: from zimbra.jrv.org ([127.0.0.1]) by localhost (zimbra.housenet.jrv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ft3ro4yXIhQJ; Mon, 20 Dec 2010 07:12:31 -0600 (CST) Received: from [10.0.2.15] (adsl-99-66-60-249.dsl.aus2tx.sbcglobal.net [99.66.60.249]) by zimbra.jrv.org (Postfix) with ESMTPSA id 138E116A046; Mon, 20 Dec 2010 07:12:31 -0600 (CST) Message-ID: <4D0F5644.7060000@jrv.org> Date: Mon, 20 Dec 2010 07:12:36 -0600 From: "James R. Van Artsdalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: Sergey Gavrilov References: <20101219123029.GM2127@garage.freebsd.pl> <4D0ED910.5010408@jrv.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Ivan Voras Subject: Re: ZFS recovery after power failure 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: Mon, 20 Dec 2010 13:12:33 -0000 On 12/20/2010 12:59 AM, Sergey Gavrilov wrote: > Could you tell about why it can damage the pool in more details, please. Once the last uberblock write in a pool during a transaction group write has completed, ZFS may start reallocating and overwriting all blocks freed in the previous transaction group. Some of those blocks may contain necessary high-level pool data and metadata from the previous uberblock. If a power failure happens and an incorrectly-deferred uberblock update never happens, yet a write to a "free" block from above does commit to media, you can wind up with no uberblocks pointing to valid pool data. v28 "fixes" this by deferring reallocation of freed blocks for 3 transaction group updates. There is still a chance of failure but in the real world the odds of failure should be very low, although a disk controller with a big enough write-back cache might still run into a problem if it doesn't handle SYNC correctly. From owner-freebsd-fs@FreeBSD.ORG Mon Dec 20 14:59:08 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F19381065672 for ; Mon, 20 Dec 2010 14:59:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id ADCF28FC15 for ; Mon, 20 Dec 2010 14:59:07 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 4FA1746B2D; Mon, 20 Dec 2010 09:59:07 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3E8628A009; Mon, 20 Dec 2010 09:59:06 -0500 (EST) From: John Baldwin To: freebsd-fs@freebsd.org Date: Mon, 20 Dec 2010 07:53:06 -0500 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20101102; KDE/4.4.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201012200753.06804.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Mon, 20 Dec 2010 09:59:06 -0500 (EST) X-Virus-Scanned: clamav-milter 0.96.3 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.9 required=4.2 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bigwig.baldwin.cx Cc: Subject: Re: debugging process in bovlbx state 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: Mon, 20 Dec 2010 14:59:08 -0000 On Sunday, December 19, 2010 7:10:04 pm Benjamin Kaduk wrote: > Hi all, > > I'm working on bringing the out-of-tree OpenAFS network filesystem > up-to-date for FreeBSD 7.3-RELEASE, and I think I need some help to fix > this bug. > I should preface my discourse with the fact that there is a whole slow of > lock order reversals that I haven't even tried to track down, but I do not > believe that this hang is deadlock since 'show alllocks' in DDB does not > show anything that seems interesting. > > Any pointers for things to look at would be appreciated; more details of > the failing case below. > > > In order to get the afs kernel module to load, I needed to tweak a few > lines of code in getpages(), as I had previously cribbed a bunch of > changes/updates from the experimental NFS client while getting AFS to work > on current freebsd. In particular, vm_page_set_valid is not present in > 7.3, so I am currently running with: > --- a/src/afs/FBSD/osi_vnodeops.c > +++ b/src/afs/FBSD/osi_vnodeops.c > @@ -890,12 +890,8 @@ afs_vop_getpages(struct vop_getpages_args *ap) > * Read operation filled a partial page. > */ > m->valid = 0; > - vm_page_set_valid(m, 0, size - toff); > -#ifndef AFS_FBSD80_ENV > - vm_page_undirty(m); > -#else > + vm_page_set_validclean(m, 0, size - toff); > KASSERT(m->dirty == 0, ("afs_getpages: page %p is dirty", m)); > -#endif > } > > > But my knowledge of vm_page_* is approximately nil, so there's no reason > to think everything was correct even before that patch. > > Anyway, my test case is running libarchive's configure script with source > and destination directories in (different places in) AFS. It only gets > twenty lines in, ending with: > checking for gcc option to accept ISO C89... none needed > checking for style of include used by make... GNU > checking dependency style of gcc... > ^Tload: 0.04 cmd: cp 1250 [bovlbx] 0.00u 0.00 > > procstat -kk reports: > mega-man# procstat -kk 1250 > PID TID COMM TDNAME KSTACK > 1250 100060 cp - mi_switch+0x233 > sleepq_switch+0xe9 sleepq_wait+0x44 _sleep+0x3a0 vm_object_pip_wait+0x4e > bufobj_invalbuf+0x10e afs_GetVCache+0x2f7 > > The call to vinvalbuf in afs_GetVCache is here: > 1646 iheldthelock = VOP_ISLOCKED(vp, curthread); This is probably wrong. VOP_ISLOCKED() can return four different values: - LK_SHARED: (someone, possibly curthread) holds a shared lock - LK_EXCLUSIVE: curthread holds an exclusive lock - LK_EXCLOTHER: some other thread holds an exclusive lock - 0: no thread holds any lock. This means if another thread has the vnode locked, you don't try to lock it. :) Do you actually know that this routine can be held without the vnode locked by the current thread? -- John Baldwin From owner-freebsd-fs@FreeBSD.ORG Tue Dec 21 15:02:49 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 329F21065672 for ; Tue, 21 Dec 2010 15:02:49 +0000 (UTC) (envelope-from am@raisa.eu.org) Received: from raisa.eu.org (raisa.eu.org [83.17.178.202]) by mx1.freebsd.org (Postfix) with ESMTP id 7ABF98FC12 for ; Tue, 21 Dec 2010 15:02:48 +0000 (UTC) Received: from arrow (127-goc-33.acn.waw.pl [94.75.108.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by raisa.eu.org (Postfix) with ESMTP id 30FB813A for ; Tue, 21 Dec 2010 15:26:30 +0100 (CET) Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Date: Tue, 21 Dec 2010 15:29:01 +0100 To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Emil Smolenski" Message-ID: User-Agent: Opera Mail/11.00 (FreeBSD) Subject: [ZFS] Booting from zpool created on 4k-sector drive 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, 21 Dec 2010 15:02:49 -0000 Hello, There is a hack to force zpool creation with minimum sector size equal to 4k: # gnop create -S 4096 ${DEV0} # zpool create tank ${DEV0}.nop # zpool export tank # gnop destroy ${DEV0}.nop # zpool import tank Zpool created this way is much faster on problematic 4k sector drives which lies about its sector size (like WD EARS). This hack works perfectly fine when system is running. Gnop layer is created only for "zpool create" command -- ZFS stores information about sector size in its metadata. After zpool creation one can export the pool, remove gnop layer and reimport the pool. Difference can be seen in the output from the zdb command: - on 512 sector device (2**9 = 512): % zdb tank |grep ashift ashift=9 - on 4096 sector device (2**12 = 4096): % zdb tank |grep ashift ashift=12 This change is permanent. The only possibility to change the value of ashift is: zpool destroy/create and restoring pool from backup. But there is one problem: I cannot boot from such pool. Error message: ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type 0 This is standard configuration with GPT scheme. # gpart show da0 => 34 2930211565 da0 GPT (1.4T) 34 30 - free - (15K) 64 128 1 freebsd-boot (64K) 192 4194304 2 freebsd-swap (2.0G) 4194496 8388608 3 freebsd-zfs (4.0G) 12583104 2917628495 - free - (1.4T) # zpool status tank pool: tank state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 gpt/tank0 ONLINE 0 0 0 # zdb -uuu tank Uberblock magic = 0000000000bab10c version = 15 txg = 2838 guid_sum = 12371721502612965633 timestamp = 1292860198 UTC = Mon Dec 20 15:49:58 2010 rootbp = [L0 DMU objset] 800L/200P DVA[0]=<0:2041000:1000> DVA[1]=<0:30062000:1000> DVA[2]=<0:ee0bd000:1000> fletcher4 lzjb LE contiguous birth=2838 fill=374 cksum=c9605617d:4e2cf0a8c94:f6decb77086a:210752c3aee4a8 There is FreeBSD 8.2-PRERELEASE installed. This is output from my lame pseudo-debug code. Format is "_func_:returncode". Examined file: zfsimpl.c: (...) vdev_probe:5 vdev_read_phys:0 nvlist_find:0 nvlist_find:0 nvlist_find:0 nvlist_find:0 nvlist_find:0 nvlist_find:5 spa_find_by_guid:0 spa_create:3621543968 nvlist_find:0 vdev_find:0 nvlist_find:0 nvlist_find:0 nvlist_find:0 nvlist_find:0 nvlist_find:5 nvlist_find:5 nvlist_find:5 nvlist_find:5 nvlist_find:5 vdev_find:0 vdev_create:3621548269 nvlist_find:0 nvlist_find:5 nvlist_find:0 nvlist_find:5 vdev_init_from_nvlist:0 vdev_find:3621548269 vdev_read_phys:5 #(condition: (bp && zio_checksum_error(bp, buf))) vdev_read_phys:5 #(condition: (bp && zio_checksum_error(bp, buf))) (...) #(many times) vdev_read_phys:5 #(condition: (bp && zio_checksum_error(bp, buf))) vdev_read_phys:5 #(condition: (bp && zio_checksum_error(bp, buf))) vdev_probe:0 zfs_alloc_temp:3620233248 ZFS: i/o error - all block copies unavailable zio_read:5 ZFS: can't read MOS zfs_mount_pool:5 ZFS: unexpected object set type 0 zfs_lookup:5 ZFS: unexpected object set type 0 zfs_lookup:5 (...) I don't know whether this information is useful. If it is not, please provide me patches with more suitable debug code. Thanks! Background information: IMO this issue is critical. Almost all >=2TB disks have 4k sector size nowadays. In the near future (>=3TB?) all disks will have 4k sectors. If I create zpool on 512 sector disks I won't be able to attach new 4k disks to it: # zpool create tank ${DEV0} # gnop create -S 4096 ${DEV1} # zpool attach tank ${DEV0} ${DEV1}.nop cannot attach ${DEV1}.nop to ${DEV0}: devices have different sector alignment Probably disks with 512 sector size will soon disappear from the market. Thus, there is need to be able to create _bootable_ zpool with 4k sector size even on 512 sector size disks. Then we can attach both 512 and 4k sector disks: # gnop create -S 4096 ${DEV1} # zpool create tank ${DEV1}.nop # zpool attach tank ${DEV1}.nop ${DEV0} # zpool status tank pool: tank state: ONLINE scrub: resilver completed after 0h0m with 0 errors on Fri Dec 17 15:47:28 2010 config: NAME STATE READ WRITE CKSUM tank ONLINE 0 0 0 mirror ONLINE 0 0 0 ${DEV1}.nop ONLINE 0 0 0 ${DEV0} ONLINE 0 0 0 448K resilvered Problem with booting prevents me from using this workaround. -- am From owner-freebsd-fs@FreeBSD.ORG Tue Dec 21 15:39:40 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94805106566C; Tue, 21 Dec 2010 15:39:39 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) by mx1.freebsd.org (Postfix) with ESMTP id 341BA8FC08; Tue, 21 Dec 2010 15:39:38 +0000 (UTC) Received: from [IPv6:::1] (ruben@erg [IPv6:2a02:898:96::5e8e:f508]) (authenticated bits=0) by erg.verweg.com (8.14.4/8.14.4) with ESMTP id oBLFdWAx079266 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 21 Dec 2010 15:39:37 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host ruben@erg [IPv6:2a02:898:96::5e8e:f508] claimed to be [IPv6:::1] Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ruben van Staveren In-Reply-To: <4D0A09AF.3040005@FreeBSD.org> Date: Tue, 21 Dec 2010 16:39:22 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <029006A4-B55F-4616-8946-0D4DF64E2D0E@verweg.com> References: <4D0A09AF.3040005@FreeBSD.org> To: Martin Matuska X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]); Tue, 21 Dec 2010 15:39:37 +0000 (UTC) Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: New ZFSv28 patchset for 8-STABLE 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, 21 Dec 2010 15:39:40 -0000 Ok, On 16 Dec 2010, at 13:44, Martin Matuska wrote: > Please test, test, test. Chances are this is the last patchset before > v28 going to HEAD (finally) and after a reasonable testing period into > 8-STABLE. > Especially test new changes, like boot support and sendfile(2) = support. > Also be sure to verify if you can import for existing ZFS pools > (v13-v15) when running v28 or boot from your existing pools. >=20 > Please test the (v13-v15) compatibility layer as well: > Old usereland + new kernel / old kernel + new userland Using v28 kernel+userland seems to work on FreeBSD/amd64, I didn't dare = to mix userland/kernel as that is ill advised by itself when there are = major changes, like this one. I can't seem to use zfs allow/userspace/groupspace. old py-zfs just = dumped core on those commands, recompiling gave my warnings about a = missing solaris.misc module which persisted even after a upgrade to = py26-zfs-1_1. Thanks for keeping up the good work on ZFS in FreeBSD! Best Regards, Ruben= From owner-freebsd-fs@FreeBSD.ORG Tue Dec 21 19:56:32 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A4CE1065741; Tue, 21 Dec 2010 19:56:32 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 10F9E8FC18; Tue, 21 Dec 2010 19:56:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBLJuVq9075977; Tue, 21 Dec 2010 19:56:31 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBLJuVPR075973; Tue, 21 Dec 2010 19:56:31 GMT (envelope-from linimon) Date: Tue, 21 Dec 2010 19:56:31 GMT Message-Id: <201012211956.oBLJuVPR075973@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/153351: [zfs] locking directories/files in ZFS 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, 21 Dec 2010 19:56:32 -0000 Synopsis: [zfs] locking directories/files in ZFS Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Tue Dec 21 19:56:15 UTC 2010 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=153351 From owner-freebsd-fs@FreeBSD.ORG Wed Dec 22 09:00:25 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C86B10656AD for ; Wed, 22 Dec 2010 09:00:25 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D4B548FC14 for ; Wed, 22 Dec 2010 09:00:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBM90Os6045030 for ; Wed, 22 Dec 2010 09:00:24 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBM90Oir045018; Wed, 22 Dec 2010 09:00:24 GMT (envelope-from gnats) Date: Wed, 22 Dec 2010 09:00:24 GMT Message-Id: <201012220900.oBM90Oir045018@freefall.freebsd.org> To: freebsd-fs@FreeBSD.org From: "Vladislav V. Prodan" Cc: Subject: Re: kern/153351: [zfs] locking directories/files in ZFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Vladislav V. Prodan" List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Dec 2010 09:00:25 -0000 The following reply was made to PR kern/153351; it has been noted by GNATS. From: "Vladislav V. Prodan" To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/153351: [zfs] locking directories/files in ZFS Date: Wed, 22 Dec 2010 10:54:53 +0200 zfs snapshot tank/www@temp zfs rollback tank/www@temp also did not help. :( -- Vladislav V. Prodan VVP24-UANIC +38[067]4584408 +38[099]4060508 vlad11@jabber.ru From owner-freebsd-fs@FreeBSD.ORG Wed Dec 22 16:31:21 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E69D106564A for ; Wed, 22 Dec 2010 16:31:21 +0000 (UTC) (envelope-from freebsd@deman.com) Received: from cp11.openaccess.org (cp11.openaccess.org [66.114.41.130]) by mx1.freebsd.org (Postfix) with ESMTP id 59B7F8FC15 for ; Wed, 22 Dec 2010 16:31:21 +0000 (UTC) Received: from mono-sis1.s.bli.openaccess.org ([66.114.32.149] helo=[192.168.2.226]) by cp11.openaccess.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1PVRax-0006Qg-Qr; Wed, 22 Dec 2010 08:31:20 -0800 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Michael DeMan In-Reply-To: Date: Wed, 22 Dec 2010 08:31:19 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <174AB79A-6767-4464-AE79-C50EFADA360E@deman.com> References: <20101219123029.GM2127@garage.freebsd.pl> To: freebsd-fs@freebsd.org X-Mailer: Apple Mail (2.1082) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cp11.openaccess.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - deman.com X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: ZFS recovery after power failure 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, 22 Dec 2010 16:31:21 -0000 Hi Sergey, I am curious on the details of how you did this in case I ever need to = do it in the future. I presume what you did was... A) grab the uberblocks off of each disk to text files using dd or = something? B) find the most recent uberblocks (they should be round robin, with = incrementing transaction group numbers so fairly easy to analyze)? C) you cleared out the most recent two uberblocks on each disk by making = their transaction group (uint64_t ub_txg) to zero or something, using dd = again? D) Did you also have to recalculate the checksum (uint64_t ub_guid_sum), = or were you able to just leave it as-is and ZFS was okay, and then = subsequently just wrote out a new/valid uber block to that position in = the array as new transactions began after you were able to get the pool = remounted? Thanks, - Mike On Dec 19, 2010, at 7:13 AM, Sergey Gavrilov wrote: > I've destroyed 2 latest uberblocks and imported pool. It's ok now. > Your command don't work for me as is, but all tgx nubmers of all = labels are > the same and equal 666999 now. > Think it's already useless information. > So I saved those uberblocks. I can provide them if you need. >=20 > 2010/12/19 Pawel Jakub Dawidek >=20 >> On Sat, Dec 18, 2010 at 11:21:52AM +0300, Sergey Gavrilov wrote: >>> zpool import -F pool2 ok, but >>> zpool status -xv >>> pool: pool2 >>> state: FAULTED >>> status: The pool metadata is corrupted and the pool cannot be = opened. >>> action: Destroy and re-create the pool from a backup source. >>> see: http://www.sun.com/msg/ZFS-8000-72 >>> scrub: none requested >>> config: >>>=20 >>> NAME STATE READ WRITE CKSUM >>> pool2 FAULTED 0 0 1 corrupted data >>> raidz2 ONLINE 0 0 6 >>> da9 ONLINE 0 0 0 >>> da10 ONLINE 0 0 0 >>> da11 ONLINE 0 0 0 >>> da12 ONLINE 0 0 0 >>> da13 ONLINE 0 0 0 >>> da14 ONLINE 0 0 0 >>> da15 ONLINE 0 0 0 >>> da16 ONLINE 0 0 0 >>>=20 >>> zpool clear pool2 >>> cannot clear errors for pool2: I/O error >>>=20 >>> Is there any way to recovery data or portion of data at least. >>=20 >> Could you provide output of: >>=20 >> # apply "zdb -l /dev/da%1 | egrep '(^LABEL|txg=3D|)'" `jot 8 9` >>=20 >> -- >> Pawel Jakub Dawidek http://www.wheelsystems.com >> pjd@FreeBSD.org http://www.FreeBSD.org >> FreeBSD committer Am I Evil? Yes, I Am! >>=20 >=20 >=20 >=20 > --=20 > Best regards, > Sergey Gavrilov > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Thu Dec 23 08:27:15 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C62F1065670; Thu, 23 Dec 2010 08:27:15 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) by mx1.freebsd.org (Postfix) with ESMTP id A8BE58FC17; Thu, 23 Dec 2010 08:27:14 +0000 (UTC) Received: from [IPv6:::1] (ruben@erg [IPv6:2a02:898:96::5e8e:f508]) (authenticated bits=0) by erg.verweg.com (8.14.4/8.14.4) with ESMTP id oBN8R8hO060691 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Dec 2010 08:27:13 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host ruben@erg [IPv6:2a02:898:96::5e8e:f508] claimed to be [IPv6:::1] Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ruben van Staveren In-Reply-To: <4D0A09AF.3040005@FreeBSD.org> Date: Thu, 23 Dec 2010 09:27:07 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <4D0A09AF.3040005@FreeBSD.org> To: Martin Matuska X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]); Thu, 23 Dec 2010 08:27:13 +0000 (UTC) Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Updated py-zfs ? Re: New ZFSv28 patchset for 8-STABLE 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, 23 Dec 2010 08:27:15 -0000 Hi, On 16 Dec 2010, at 13:44, Martin Matuska wrote: > Hi everyone, >=20 > following the announcement of Pawel Jakub Dawidek (pjd@FreeBSD.org) I = am > providing a ZFSv28 testing patch for 8-STABLE. Where can I find an updated py-zfs so that zfs = (un)allow/userspace/groupspace can be tested ? Regards, Ruben From owner-freebsd-fs@FreeBSD.ORG Thu Dec 23 08:58:57 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4895106566B; Thu, 23 Dec 2010 08:58:57 +0000 (UTC) (envelope-from mm@FreeBSD.org) Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:100:1043::3]) by mx1.freebsd.org (Postfix) with ESMTP id 6BC6C8FC14; Thu, 23 Dec 2010 08:58:57 +0000 (UTC) Received: from core.vx.sk (localhost [127.0.0.1]) by mail.vx.sk (Postfix) with ESMTP id 94F5C1322B6; Thu, 23 Dec 2010 09:58:56 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.vx.sk Received: from mail.vx.sk ([127.0.0.1]) by core.vx.sk (mail.vx.sk [127.0.0.1]) (amavisd-new, port 10024) with LMTP id dT4Gf1tTh0FT; Thu, 23 Dec 2010 09:58:54 +0100 (CET) Received: from [10.9.8.1] (188-167-78-139.dynamic.chello.sk [188.167.78.139]) by mail.vx.sk (Postfix) with ESMTPSA id 8AC4D1322AE; Thu, 23 Dec 2010 09:58:54 +0100 (CET) Message-ID: <4D130F4E.3040701@FreeBSD.org> Date: Thu, 23 Dec 2010 09:58:54 +0100 From: Martin Matuska User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sk; rv:1.8.1.23) Gecko/20090812 Lightning/0.9 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 MIME-Version: 1.0 To: Ruben van Staveren References: <4D0A09AF.3040005@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Updated py-zfs ? Re: New ZFSv28 patchset for 8-STABLE 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, 23 Dec 2010 08:58:57 -0000 I have updated the py-zfs port right now so it should work with v28, too. The problem was a non-existing solaris.misc module, I had to patch and remove references to this module. Cheers, mm Dňa 23.12.2010 09:27, Ruben van Staveren wrote / napísal(a): > Hi, > > On 16 Dec 2010, at 13:44, Martin Matuska wrote: > >> Hi everyone, >> >> following the announcement of Pawel Jakub Dawidek (pjd@FreeBSD.org) I am >> providing a ZFSv28 testing patch for 8-STABLE. > > Where can I find an updated py-zfs so that zfs (un)allow/userspace/groupspace can be tested ? > > Regards, > Ruben > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Thu Dec 23 09:46:33 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ABB31065679; Thu, 23 Dec 2010 09:46:33 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]) by mx1.freebsd.org (Postfix) with ESMTP id A347A8FC1E; Thu, 23 Dec 2010 09:46:32 +0000 (UTC) Received: from [IPv6:::1] (ruben@erg [IPv6:2a02:898:96::5e8e:f508]) (authenticated bits=0) by erg.verweg.com (8.14.4/8.14.4) with ESMTP id oBN9kQ21066000 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Dec 2010 09:46:31 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host ruben@erg [IPv6:2a02:898:96::5e8e:f508] claimed to be [IPv6:::1] Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii From: Ruben van Staveren In-Reply-To: <4D130F4E.3040701@FreeBSD.org> Date: Thu, 23 Dec 2010 10:46:20 +0100 Content-Transfer-Encoding: 7bit Message-Id: <1779BD6F-12D5-434E-99FA-BB33DC273998@verweg.com> References: <4D0A09AF.3040005@FreeBSD.org> <4D130F4E.3040701@FreeBSD.org> To: Martin Matuska X-Mailer: Apple Mail (2.1082) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (erg.verweg.com [IPv6:2a02:898:96::5e8e:f508]); Thu, 23 Dec 2010 09:46:31 +0000 (UTC) Cc: freebsd-fs@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Updated py-zfs ? Re: New ZFSv28 patchset for 8-STABLE 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, 23 Dec 2010 09:46:33 -0000 Thanks, I'm going to check it out! On 23 Dec 2010, at 9:58, Martin Matuska wrote: > I have updated the py-zfs port right now so it should work with v28, > too. The problem was a non-existing solaris.misc module, I had to patch > and remove references to this module. > > Cheers, > mm > Regards, Ruben From owner-freebsd-fs@FreeBSD.ORG Thu Dec 23 12:03:26 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 402CE106566B for ; Thu, 23 Dec 2010 12:03:26 +0000 (UTC) (envelope-from srg.gavrilov@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 031728FC21 for ; Thu, 23 Dec 2010 12:03:25 +0000 (UTC) Received: by iwn39 with SMTP id 39so6139044iwn.13 for ; Thu, 23 Dec 2010 04:03:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ADCcD8zOzS01YOwZU/A74/m4/XMbr9IWOxJAPiSfyBg=; b=aSc0yBF5TVNMzP/iBkV2faQIeSYoj+jGXI25qgtNlEK7Hood/GO81Jv7+J9oWdOVy3 Eu/Xpp+OGP+ZC6YLqPobH7KZTWlOyjnaxOuBodRUuDtpEbwB7aRjnbHqDs67Q3eYI2Sm RvA1sdzrwTAudz7ZMdyoDLZkjKkgJFLhPa37w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LxiT1q72Np+7kGiNXEkgSR/RI3cLULQugbYU223/hxnHjNy+fykh3jJBO+1jG0AY5Y Csfw0erZ2cce5hMD8yN7kAJB5BMmmW/vXoSi4lGmqgbCEmEBw53IGQl8qiH9I/dX4STY Yfm6tEzXm7d2AZLS96yOaVZHv7jBhae1G49qs= MIME-Version: 1.0 Received: by 10.42.178.69 with SMTP id bl5mr8215308icb.338.1293105805392; Thu, 23 Dec 2010 04:03:25 -0800 (PST) Received: by 10.42.150.65 with HTTP; Thu, 23 Dec 2010 04:03:25 -0800 (PST) In-Reply-To: <174AB79A-6767-4464-AE79-C50EFADA360E@deman.com> References: <20101219123029.GM2127@garage.freebsd.pl> <174AB79A-6767-4464-AE79-C50EFADA360E@deman.com> Date: Thu, 23 Dec 2010 15:03:25 +0300 Message-ID: From: Sergey Gavrilov To: Michael DeMan Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS recovery after power failure 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, 23 Dec 2010 12:03:26 -0000 Hi Michael, yes I walked the way you describe. I just destroyed whole uberblock, not only ub_txg. So I think it's not important. And I didn't recalculate ub_guid_sum. Isn't it similar in all uberblocks? 2010/12/22 Michael DeMan > Hi Sergey, > > I am curious on the details of how you did this in case I ever need to do > it in the future. > > > I presume what you did was... > > A) grab the uberblocks off of each disk to text files using dd or > something? > > B) find the most recent uberblocks (they should be round robin, with > incrementing transaction group numbers so fairly easy to analyze)? > > C) you cleared out the most recent two uberblocks on each disk by making > their transaction group (uint64_t ub_txg) to zero or something, using dd > again? > > D) Did you also have to recalculate the checksum (uint64_t ub_guid_sum), or > were you able to just leave it as-is and ZFS was okay, and then subsequently > just wrote out a new/valid uber block to that position in the array as new > transactions began after you were able to get the pool remounted? > > Thanks, > > - Mike > > > On Dec 19, 2010, at 7:13 AM, Sergey Gavrilov wrote: > > > I've destroyed 2 latest uberblocks and imported pool. It's ok now. > > Your command don't work for me as is, but all tgx nubmers of all labels > are > > the same and equal 666999 now. > > Think it's already useless information. > > So I saved those uberblocks. I can provide them if you need. > > > > 2010/12/19 Pawel Jakub Dawidek > > > >> On Sat, Dec 18, 2010 at 11:21:52AM +0300, Sergey Gavrilov wrote: > >>> zpool import -F pool2 ok, but > >>> zpool status -xv > >>> pool: pool2 > >>> state: FAULTED > >>> status: The pool metadata is corrupted and the pool cannot be opened. > >>> action: Destroy and re-create the pool from a backup source. > >>> see: http://www.sun.com/msg/ZFS-8000-72 > >>> scrub: none requested > >>> config: > >>> > >>> NAME STATE READ WRITE CKSUM > >>> pool2 FAULTED 0 0 1 corrupted data > >>> raidz2 ONLINE 0 0 6 > >>> da9 ONLINE 0 0 0 > >>> da10 ONLINE 0 0 0 > >>> da11 ONLINE 0 0 0 > >>> da12 ONLINE 0 0 0 > >>> da13 ONLINE 0 0 0 > >>> da14 ONLINE 0 0 0 > >>> da15 ONLINE 0 0 0 > >>> da16 ONLINE 0 0 0 > >>> > >>> zpool clear pool2 > >>> cannot clear errors for pool2: I/O error > >>> > >>> Is there any way to recovery data or portion of data at least. > >> > >> Could you provide output of: > >> > >> # apply "zdb -l /dev/da%1 | egrep '(^LABEL|txg=|)'" `jot 8 9` > >> > >> -- > >> Pawel Jakub Dawidek http://www.wheelsystems.com > >> pjd@FreeBSD.org http://www.FreeBSD.org > >> FreeBSD committer Am I Evil? Yes, I Am! > >> > > > > > > > > -- > > Best regards, > > Sergey Gavrilov > > _______________________________________________ > > freebsd-fs@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > > -- Best regards, Sergey Gavrilov From owner-freebsd-fs@FreeBSD.ORG Thu Dec 23 17:17:00 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC7BD1065673 for ; Thu, 23 Dec 2010 17:17:00 +0000 (UTC) (envelope-from jcw@speakeasy.net) Received: from mail2.sea5.speakeasy.net (mail2.sea5.speakeasy.net [69.17.117.41]) by mx1.freebsd.org (Postfix) with ESMTP id 8C31B8FC12 for ; Thu, 23 Dec 2010 17:17:00 +0000 (UTC) Received: (qmail 13922 invoked from network); 23 Dec 2010 16:48:37 -0000 Received: from s5.stradamotorsports.com (HELO w16.stradamotorsports.com) (jcw@[64.81.163.123]) (envelope-sender ) by mail2.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 23 Dec 2010 16:48:37 -0000 Message-ID: <4D137D65.6040502@speakeasy.net> Date: Thu, 23 Dec 2010 08:48:37 -0800 From: "Jason C. Wells" User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.10) Gecko/20100808 Lightning/1.0b1 Thunderbird/3.0.5 MIME-Version: 1.0 To: freebsd-fs@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 23 Dec 2010 17:47:53 +0000 Cc: Subject: Mount Union Only at One Hierachy Level 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, 23 Dec 2010 17:17:00 -0000 'mount -o union' cannot properly overlay namespaces at more than one level of the hierarchy. Another way of saying this is that 'mount -o union' doesn't manage namespace collisions in a unioned way. Notice the duplicate . and .. and usr directories: # ls -la drwxr-xr-x 7 root wheel 512 Dec 23 16:16 . drwxr-xr-x 7 root wheel 512 Dec 23 16:16 . drwxr-xr-x 7 root wheel 512 Dec 21 13:55 .. drwxr-xr-x 7 root wheel 512 Dec 21 13:55 .. drwxr-xr-x 2 root wheel 1024 Jul 19 02:24 bin ... drwxr-xr-x 3 root wheel 512 Dec 23 16:15 usr drwxr-xr-x 3 root wheel 512 Dec 23 16:15 usr drwxr-xr-x 21 root wheel 512 Dec 23 05:34 var To achieve this I did; # mount -t nullfs -o union,rw /usr/jail/f1 /usr/jail/f1-fs where ./f1 contains the jail's ./usr, but without ./usr/local and ./f1-fs contains only ./usr/local. I expect the namespaces to be unioned at /usr/jail/f1, but they were not. Only ./usr/local is accessible. ./usr/bin and friends are not accessible. I did this because I desired ./usr to be read only, but ./usr/local to be read write so I could add packages inside the jail. I know I can do this another way. The question is, is this a bug? Regards, Jason C. Wells From owner-freebsd-fs@FreeBSD.ORG Thu Dec 23 23:17:49 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C624106566B; Thu, 23 Dec 2010 23:17:49 +0000 (UTC) (envelope-from jhellenthal@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3C7328FC13; Thu, 23 Dec 2010 23:17:48 +0000 (UTC) Received: by gwj21 with SMTP id 21so4015513gwj.13 for ; Thu, 23 Dec 2010 15:17:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=3fTQIxocJ1HiVqMaCthQNj8iWTE5/J+8YWeU/eD7G1c=; b=oB0CnkUZpCGsHPsNHDXZMup2PuNeB3Crce3UuZSOQJEuhvi6VHKiasAMknuYZi1ZdY kTwM+MjMqgsY8fg4nzhfUwhOEh7xfM1sinZz0E/zhn3JsouHdOrWOSt7eXQ5lsAYN7u1 B4jdwiBHzouNgOglrNvzofvC1grUHVPKgMYbE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=e27vvZQxrB2juUVGLkj+jVI8lq0SA296fVPsHV4kDdxwqXVM27E/0J1Lh3mJrdFbxT 0Q298P4iHjOioZ/AFTLbmB9o8BW9dwP1KWXIwzTXzUDObm14OJEbcCzyteQFEKJkbAfS 4dWqntQtQDURE5JJQH6BH5Py5r6IgK9XGIFnQ= Received: by 10.150.196.2 with SMTP id t2mr12816661ybf.205.1293146268309; Thu, 23 Dec 2010 15:17:48 -0800 (PST) Received: from centel.dataix.local (adsl-99-181-145-144.dsl.klmzmi.sbcglobal.net [99.181.145.144]) by mx.google.com with ESMTPS id 8sm4662304yhx.3.2010.12.23.15.17.45 (version=SSLv3 cipher=RC4-MD5); Thu, 23 Dec 2010 15:17:46 -0800 (PST) Sender: "J. Hellenthal" Message-ID: <4D13D898.6040203@DataIX.net> Date: Thu, 23 Dec 2010 18:17:44 -0500 From: jhell Organization: http://www.DataIX.net User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.13) Gecko/20101210 Lightning/1.0b1 Thunderbird MIME-Version: 1.0 To: Martin Matuska References: <4D0A09AF.3040005@FreeBSD.org> In-Reply-To: <4D0A09AF.3040005@FreeBSD.org> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: New ZFSv28 patchset for 8-STABLE 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, 23 Dec 2010 23:17:49 -0000 Hi Martin, List, Patched up to a ZFSv28 20101218 and it is working as expected, Great Job!. There seems to be some assertion errors that are left to be fixed yet with the following examples: Panic String: solaris assert: vd->vdev_stat.vs_alloc == 0 (0x18a000 == 0x0), file:/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c, line: 4623 #3 0x84caca35 in spa_vdev_remove (spa=0x84dba000, guid=2330662286000872312, unspare=0) at /usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/spa.c:4623 4623 ASSERT3U(vd->vdev_stat.vs_alloc, ==, 0); (kgdb) list 4618 4619 /* 4620 * The evacuation succeeded. Remove any remaining MOS metadata 4621 * associated with this vdev, and wait for these changes to sync. 4622 */ 4623 ASSERT3U(vd->vdev_stat.vs_alloc, ==, 0); 4624 txg = spa_vdev_config_enter(spa); 4625 vd->vdev_removing = B_TRUE; 4626 vdev_dirty(vd, 0, NULL, txg); 4627 vdev_config_dirty(vd); This happens on i386 upon ( zfs remove pool ) Also if it is of any relevance this happens during ``offline'' too. If further information is needed I still have these cores and kernel just let me know what you need. Regards, -- jhell,v From owner-freebsd-fs@FreeBSD.ORG Fri Dec 24 19:56:53 2010 Return-Path: Delivered-To: freebsd-fs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6D0F106564A; Fri, 24 Dec 2010 19:56:53 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BD6C28FC0C; Fri, 24 Dec 2010 19:56:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oBOJurhl029610; Fri, 24 Dec 2010 19:56:53 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oBOJurKh029606; Fri, 24 Dec 2010 19:56:53 GMT (envelope-from linimon) Date: Fri, 24 Dec 2010 19:56:53 GMT Message-Id: <201012241956.oBOJurKh029606@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-fs@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/153418: [zfs] [panic] Kernel Panic occurred writing to zfs volume via nfs. 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: Fri, 24 Dec 2010 19:56:54 -0000 Old Synopsis: Kernel Panic occurred writing to zfs volume via nfs. New Synopsis: [zfs] [panic] Kernel Panic occurred writing to zfs volume via nfs. Responsible-Changed-From-To: freebsd-amd64->freebsd-fs Responsible-Changed-By: linimon Responsible-Changed-When: Fri Dec 24 19:56:32 UTC 2010 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=153418 From owner-freebsd-fs@FreeBSD.ORG Sat Dec 25 14:31:14 2010 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3193106566B for ; Sat, 25 Dec 2010 14:31:13 +0000 (UTC) (envelope-from void@list.ru) Received: from fallback3.mail.ru (fallback6.mail.ru [94.100.176.134]) by mx1.freebsd.org (Postfix) with ESMTP id 5BAA58FC13 for ; Sat, 25 Dec 2010 14:31:12 +0000 (UTC) Received: from smtp1.mail.ru (smtp1.mail.ru [94.100.176.129]) by fallback3.mail.ru (mPOP.Fallback_MX) with ESMTP id 4D521A16EAC for ; Sat, 25 Dec 2010 17:17:09 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail; h=Content-Type:MIME-Version:Message-ID:Date:Subject:To:From; bh=CS7fc6L/GxluRi4zS1oYGIxGCm5EZjhtzkzyU43Br1E=; b=e+jAvU9x4ytNrU4XzFLuzMPUMJCwk8OeidLtIyNqob9qxqGrztxls1g0N5NfHyhJEUmbUElusv2yo6FBOjt5YQV9GO3B5STjTl7GxpfeKR/93cb2XqZ7YW9ZVm66TXNn; Received: from [92.252.158.238] (port=1372 helo=COMP1) by smtp1.mail.ru with asmtp id 1PWUvj-0006kj-00 for freebsd-fs@FreeBSD.org; Sat, 25 Dec 2010 17:17:07 +0300 From: "void" To: Date: Sat, 25 Dec 2010 17:17:05 +0300 Message-ID: <514BA5D75A82411CBE80ECF0303FD425@COMP1> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcukPmhWsm1nBCRdT8KPB7Ckv5y+LQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-Spam: Not detected X-Mras: Ok X-Mailman-Approved-At: Sat, 25 Dec 2010 14:34:39 +0000 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: hello 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: Sat, 25 Dec 2010 14:31:14 -0000 Hello. Could you help me please? I trying configure hastd, but i have a problem. root@ul-farm etc#hastd hastd: remote address not configured for resource shared root@ul-farm etc#cat /etc/hast.conf # Global section control uds:///var/run/hastctl replication fullsync timeout 5 resource shared { local /dev/da0s2 on host1 { remote tcp4://10.15.0.127 } on host2 { remote tcp4://10.15.0.1 } } I don`t understand, where is problem. =(