From owner-freebsd-fs@FreeBSD.ORG Sat Apr 28 12:05:49 2012 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 021C3106566B for ; Sat, 28 Apr 2012 12:05:49 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas01p.mx.bigpond.com (nschwmtas01p.mx.bigpond.com [61.9.189.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7A4068FC0A for ; Sat, 28 Apr 2012 12:05:46 +0000 (UTC) Received: from nschwotgx04p.mx.bigpond.com ([124.188.161.100]) by nschwmtas01p.mx.bigpond.com with ESMTP id <20120428120544.UZUY24679.nschwmtas01p.mx.bigpond.com@nschwotgx04p.mx.bigpond.com>; Sat, 28 Apr 2012 12:05:44 +0000 Received: from johnny.reilly.home ([124.188.161.100]) by nschwotgx04p.mx.bigpond.com with ESMTP id <20120428120544.FDCW1687.nschwotgx04p.mx.bigpond.com@johnny.reilly.home>; Sat, 28 Apr 2012 12:05:44 +0000 Date: Sat, 28 Apr 2012 22:05:34 +1000 From: Andrew Reilly To: Peter Maloney Message-ID: <20120428120534.GA1953@johnny.reilly.home> References: <20120424143014.GA2865@johnny.reilly.home> <4F96BAB9.9080303@brockmann-consult.de> <20120424232136.GA1441@johnny.reilly.home> <4F981A0D.40507@brockmann-consult.de> <20120426033314.GA9016@johnny.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120426033314.GA9016@johnny.reilly.home> User-Agent: Mutt/1.4.2.3i X-SIH-MSG-ID: qBkxGNz7TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rAIudRsM6kxDxEJhuHNGElaajgTY3Rs9uK Cc: freebsd-fs@freebsd.org Subject: Re: Odd file system corruption in ZFS pool 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, 28 Apr 2012 12:05:49 -0000 On Thu, Apr 26, 2012 at 01:33:14PM +1000, Andrew Reilly wrote: > Seems to be only associated with the filesystem, rather than the > pool. Well, my "tank" pool, (the raidz) shows zpool scrub > making 0 fixes but there being unrecoverable erorrs in > tank/home:<0x0>, but my backup file system (the one I send > snapshot deltas to) shows exactly the same errors with no tank > problems. (Hmm. Hold that thought: I haven't actually tried a > scrub on the backup file system. It's just zpool status that > shows no errors. Running a scrub now. Will take a while: it's > a fairly slow USB2-connected disk. Zpool status says expect 10+ > hours...) Just want to update this: zpool scrub on the bkp2pool finished with zero errors found, but the filesystem corruption noticed in the main pool (tank/home) has been faithfully reproduced. That is: I have a directory Maildir.bad that echo .* shows: Maildir.bad/. Maildir.bad/.. Maildir.bad/.AppleDouble Maildir.bad/.Suppliers.2010 Maildir.bad/.Unix But the .Suppliers.2010 entry does not seem to have an inode number (let alone an inode): $ ls -ai Maildir.bad returns: ls: .Suppliers.2010: No such file or directory 7906 . 7810 .. 82016 .AppleDouble 80774 .Unix Is this not terminally weird? Is there any way to de-confuse ZFS? Since memtest86+ did not seem to boot properly on this system, I've ordered new memory (twice as much: will be 8G now.) Also ordered a UPS. We'll see if that helps with anything. Cheers, -- Andrew