From owner-freebsd-fs@FreeBSD.ORG Sun Jan 24 13:44:34 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 9F4AD106566B for ; Sun, 24 Jan 2010 13:44:34 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 2CCED8FC0C for ; Sun, 24 Jan 2010 13:44:33 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 16so557462fgg.13 for ; Sun, 24 Jan 2010 05:44:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=JNNQyC5GDhg7Pb5VvcG/vBRl2siqK7BJGsw8jpOb4II=; b=CTARryoj36x7s+t5d00G4n7b0Is2IpFg9MvqAM0aqWdk5lCFLGD6/SakBU0UmT6xCS U1c+HD+3fjPqloipZj16eA6o95X39x8xbKkEWwOeMILNZQzZW8ALIvEfy4671f18Qh0P ffIoCXYL16Cvt1nI/1KmeCgCEp/pvY9N4vxBk= 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:content-transfer-encoding; b=Zllm3lgCfHolSI24vvY2vFvTN4L2UzEYe/7ngsYb6YGS9eFUOnWIDcDB7Tq83NrGnY 6KkQCMC0D6RmQwSi8qhlF6YmNGtklWcDIUG2fzLGFYNE264fa+iNYjLvhe8vNZ/Sa8Bs 0Mokk3ZENkAubmT6sT7jUsFQ2045jz24b2BeA= MIME-Version: 1.0 Received: by 10.239.163.67 with SMTP id o3mr588682hbd.22.1264340672804; Sun, 24 Jan 2010 05:44:32 -0800 (PST) In-Reply-To: References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <5da0588e1001231615t37c22575uedaae938be40f530@mail.gmail.com> <4B5B94B8.7070509@modulus.org> <5da0588e1001231638i349f8f17t297e970b08825441@mail.gmail.com> <5da0588e1001232017m6c67731fwaa1d71cd86800017@mail.gmail.com> <5da0588e1001232128w5a551674od0805c2ff0b884ad@mail.gmail.com> Date: Sun, 24 Jan 2010 08:44:32 -0500 Message-ID: <5da0588e1001240544q61e3bebbka7ad1248343be26d@mail.gmail.com> From: Rich To: Wes Morgan Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Errors on a file on a zpool: How to remove? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jan 2010 13:44:34 -0000 > This is a non-redundant pool. The remove command will not work. Replace > will, but for that pool to function at all, *every* device must be > present. If the metadata was recoverable, I think that the scrub would > have reported "xxx kb repaired". Actually, zpool remove can't be used for that either - zpool detach gets used for anything that's "live". > From http://dlc.sun.com/osol/docs/content/ZFSADMIN/gbbwl.html: > > =A0 =A0If the object number to a file path cannot be successfully transla= ted, > =A0 =A0either due to an error or because the object doesn't have a real f= ile > =A0 =A0path associated with it , as is the case for a dnode_t, then the > =A0 =A0dataset name followed by the object's number is displayed. For > =A0 =A0example: > > =A0 =A0 monkey/dnode:<0x0> > > Which seems to be precisely your error. Continuing: > > =A0 =A0Then, try removing the file with the rm command. If this command > =A0 =A0doesn't work, the corruption is within the file's metadata, and ZF= S > =A0 =A0cannot determine which blocks belong to the file in order to remov= e > =A0 =A0the corruption. > > =A0 =A0If the corruption is within a directory or a file's metadata, the = only > =A0 =A0choice is to move the file elsewhere. You can safely move any file= or > =A0 =A0directory to a less convenient location, allowing the original obj= ect > =A0 =A0to be restored in place." > > In other words, either move the files out of the way or restore the pool. > I'd wager that any other filesystem would have simply wiped out entire > directory trees or possibly just panicked with this kind of corruption. I'm presuming you mean "to another FS", since we already saw rm reports EIE= IO. I've started that process, and I'll get out the backups for all the other d= ata. Thanks to everyone for being so helpful, and especially to you, Wes, for citing exactly what was going on with the manual. All hail manuals! :) - Rich