From owner-freebsd-fs@FreeBSD.ORG Mon Oct 29 09:17:37 2012 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F55BA70; Mon, 29 Oct 2012 09:17:37 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 80BFD8FC15; Mon, 29 Oct 2012 09:17:36 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id b5so3687657lbd.13 for ; Mon, 29 Oct 2012 02:17:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=aHAqyh2icpx5GCbgiw7pTFcyYGs3zdp3L2ygTb3D6sM=; b=kQLVr8Y7IYMWFwCSlETpVvp2Jv8ZjdAeIanV4M0RJZaHQFr1lthkGRXxMONsb7KjuF Ynpn19/cszfAiI/nBsHCwfooFSsvLypl/M7ucYe8H7DqlnLi/gWZxE+KtyaG5o9+tWIS YdbGY4PWksmdAWXc1yp+VnkShJ9AAtKCdLyAFgHbi+S3XvupB3qTt36fNtlBbmjm/eTY +5C7nlxmd1D7xW9K9SfuOh1Yd2a1LiWRh6c1+Kyps06MOCZJdd3jzjP9p+eJnAHC+Pgq S+092d2JN3VpjsOQYF2oURhht9dAG6IUxYszMototUI6y6NaU4Pe+llPnyU+a5Uoyv2Q NmvQ== Received: by 10.152.105.236 with SMTP id gp12mr26821061lab.35.1351502255424; Mon, 29 Oct 2012 02:17:35 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id p9sm2941518lbc.3.2012.10.29.02.17.34 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2012 02:17:34 -0700 (PDT) Sender: Alexander Motin Message-ID: <508E49AD.4090501@FreeBSD.org> Date: Mon, 29 Oct 2012 11:17:33 +0200 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Lawrence Stewart Subject: Re: graid often resyncs raid1 array after clean reboot/shutdown References: <508E0C3F.8080602@freebsd.org> <508E3E81.9010209@FreeBSD.org> In-Reply-To: <508E3E81.9010209@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2012 09:17:37 -0000 On 29.10.2012 10:29, Alexander Motin wrote: > Hi. > > On 29.10.2012 06:55, Lawrence Stewart wrote: >> I have a fairly new HP Compaq 8200 Elite desktop PC with 2 x 1TB Seagate >> ST1000DM003 HDDs in raid1 using the on-board Intel Matrix RAID >> controller. The system is configured to boot from ZFS off the raid1 >> array, and I use it as a KDE GUI (with on-cpu GPU + KMS) desktop. >> >> Everything works great, except that after a "shutdown -r now" of the >> system, graid almost always (I believe I've noted a few times where >> everything comes up fine) detects one of the disks in the array as stale >> and does a full resync of the array over the course of a few hours. >> Here's an example of what I see when starting up: > > From log messages it indeed looks like result of unclean shutdown. I've > never seen such problem with UFS, but I never tested graid with ZFS. I > guess there may be some difference in shutdown process that makes RAID > metadata to have dirty flag on reboot. I'll try to reproduce it now. I confirm the problem. Seems it happens only when using ZFS as root file system. Probably ZFS issues some last moment write that makes volume dirty. I will trace it more. -- Alexander Motin