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