From owner-freebsd-fs@FreeBSD.ORG  Tue Jul 27 15:17:58 2010
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
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 D1E651065670
	for <freebsd-fs@FreeBSD.org>; Tue, 27 Jul 2010 15:17:58 +0000 (UTC)
	(envelope-from avg@icyb.net.ua)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
	by mx1.freebsd.org (Postfix) with ESMTP id 2CCD18FC15
	for <freebsd-fs@FreeBSD.org>; Tue, 27 Jul 2010 15:17:57 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
	[212.40.38.101])
	by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id SAA16178
	for <freebsd-fs@FreeBSD.org>; Tue, 27 Jul 2010 18:17:56 +0300 (EEST)
	(envelope-from avg@icyb.net.ua)
Message-ID: <4C4EF8A4.1060603@icyb.net.ua>
Date: Tue, 27 Jul 2010 18:17:56 +0300
From: Andriy Gapon <avg@icyb.net.ua>
User-Agent: Thunderbird 2.0.0.24 (X11/20100517)
MIME-Version: 1.0
To: freebsd-fs@FreeBSD.org
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: 
Subject: strange zfs pool status/error
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jul 2010 15:17:58 -0000

$ zpool status -v
  pool: pond
 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: none requested
config:

        NAME                                            STATE     READ WRITE CKSUM
        pond                                            ONLINE       0     0     0
          mirror                                        ONLINE       0     0     0
            gptid/fcf3558b-493b-11de-a8b9-001cc08221ff  ONLINE       0     0     0
            gptid/48782c6e-8fbd-11de-b3e1-00241d20d446  ONLINE       0     0     0

errors: Permanent errors have been detected in the following files:

        /usr/src/cscope.out

I don't see any errors or suspicious messages in any logs.
The file in question is perfectly readable (produces stable md5 checksum without
any errors) and apparently is not too (or at all) corrupt - cscope still works
fine with it.
All vdevs are online and there are no vdev errors.

So what does all this mean and how it can happen?
In other words, why/how did ZFS decide that that file is corrupted?

-- 
Andriy Gapon