From owner-freebsd-fs@FreeBSD.ORG Sat Jan 23 23:34:46 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 7ACB81065679 for ; Sat, 23 Jan 2010 23:34:46 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from warped.bluecherry.net (unknown [IPv6:2001:440:eeee:fffb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0147D8FC1C for ; Sat, 23 Jan 2010 23:34:46 +0000 (UTC) Received: from volatile.chemikals.org (adsl-67-214-156.shv.bellsouth.net [98.67.214.156]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by warped.bluecherry.net (Postfix) with ESMTPSA id E856590A7B00; Sat, 23 Jan 2010 17:34:44 -0600 (CST) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.3/8.14.3) with ESMTP id o0NNYfeM004748; Sat, 23 Jan 2010 17:34:41 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Sat, 23 Jan 2010 17:34:41 -0600 (CST) From: Wes Morgan X-X-Sender: morganw@volatile To: Rich In-Reply-To: <5da0588e1001231415t403f29ceq6e8dcd16edb4a28@mail.gmail.com> Message-ID: References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> <5da0588e1001231415t403f29ceq6e8dcd16edb4a28@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3224958491-771498596-1264289681=:2160" X-Virus-Scanned: clamav-milter 0.95.3 at warped X-Virus-Status: Clean Cc: freebsd-fs 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: Sat, 23 Jan 2010 23:34:46 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3224958491-771498596-1264289681=:2160 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT On Sat, 23 Jan 2010, Rich wrote: > On Sat, Jan 23, 2010 at 4:21 PM, Wes Morgan wrote: > > On Sat, 23 Jan 2010, Rich wrote: > > > >> I already diagnosed the bad hardware - one of the two sticks of RAM > >> had gone bad, and fails memtest in the other machine. > >> > >>   pool: rigatoni > >>  state: ONLINE > >> status: One or more devices has experienced an error resulting in data > >>       corruption.  Applications may be affected. > >> action: Restore the file in question if possible.  Otherwise restore the > >>       entire pool from backup. > >>    see: http://www.sun.com/msg/ZFS-8000-8A > >>  scrub: scrub completed after 15h28m with 1 errors on Thu Jan 21 18:09:25 2010 > >> config: > >> > >>       NAME        STATE     READ WRITE CKSUM > >>       rigatoni    ONLINE       0     0     1 > >>         da4       ONLINE       0     0     2 > >>         da5       ONLINE       0     0     2 > >>         da7       ONLINE       0     0     0 > >>         da6       ONLINE       0     0     0 > >>         da2       ONLINE       0     0     2 > >> > >> errors: Permanent errors have been detected in the following files: > >> > >>         rigatoni/mirrors:<0x0> > > > > Can you post your entire pool filesystem structure? That message above > > looks like an unreferenced block or corrupted metadata rather than an > > actual file. Also, if it's part of a snapshot, you simply have to destroy > > the snapshot. > > > > I had a pool become corrupted due to bad memory, and all of the files were > > still able to be manipulated. The only time EIO popped up was on the > > specific block that had a checksum error. > > # zfs list -r -t all rigatoni > NAME USED AVAIL REFER MOUNTPOINT > rigatoni 5.73T 984G 19K /rigatoni > rigatoni/logs_bitch 269M 984G 269M /rigatoni/logs_bitch > rigatoni/mirrors 5.73T 984G 5.73T /mirrors > > No snapshots here. :/ > > EIO only pops up on the files I mentioned above - everything else in > those directories, including renaming that directory, is fine. I must have missed it, what files is it showing besides the <0x0> address? Or do you have a file named "<0x0>"? --3224958491-771498596-1264289681=:2160--