From owner-freebsd-fs@FreeBSD.ORG Mon Oct 29 14:25:23 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 4E33544A; Mon, 29 Oct 2012 14:25:23 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 878B28FC16; Mon, 29 Oct 2012 14:25:22 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id e12so4852557lag.13 for ; Mon, 29 Oct 2012 07:25:21 -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=2dOhxsWuOlH96RA1OZQVo0zzz1lKIvPbCWsgpEKo1b4=; b=LBHvQTPNDRIn9fLpkT5Bz1V9MzSxmWFJHW3EDu1AWVoSZOZg12znlJEIQFlizwnfG1 3PvX7+8vxMeX52yzeMrmznvLH1ui2F9JuuqqzdgRkAIHzBn68Q3rVQhUN35BJBzkShhg ZJZilJGiOMBzvxDDUlYwntTc6mi2JZRpOIIwpAQM89rWmY2bT8WH9F2H0+uPTxiiU8D0 6fptADMj9xpLnes9MpmWUb2rTwJTCvyXM7OK5yxCG/yZjlP3g/GsAzzeRyY5KZiEWNnD VxIH/2OUXjuMIjfFmM5Tarx+mbVBl+KInsDz0JK7hIzVErTXU1J5OEnAea1FygIRfxzg D+9w== Received: by 10.112.48.74 with SMTP id j10mr12044574lbn.94.1351520721267; Mon, 29 Oct 2012 07:25:21 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (mavhome.mavhome.dp.ua. [213.227.240.37]) by mx.google.com with ESMTPS id hu6sm3166575lab.13.2012.10.29.07.25.20 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2012 07:25:20 -0700 (PDT) Sender: Alexander Motin Message-ID: <508E91CF.5070003@FreeBSD.org> Date: Mon, 29 Oct 2012 16:25:19 +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> <508E49AD.4090501@FreeBSD.org> In-Reply-To: <508E49AD.4090501@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 14:25:23 -0000 On 29.10.2012 11:17, Alexander Motin wrote: > 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. I've found problem in the fact that ZFS seems doesn't close devices on shutdown. That doesn't allow graid to shutdown gracefully. r242314 in HEAD fixes that by more aggressively marking volumes clean on shutdown. -- Alexander Motin