From owner-freebsd-questions@FreeBSD.ORG Wed Jan 8 21:09:21 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B7121AD6; Wed, 8 Jan 2014 21:09:21 +0000 (UTC) Received: from yoshi.bluerosetech.com (yoshi.bluerosetech.com [174.136.100.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E0901236; Wed, 8 Jan 2014 21:09:21 +0000 (UTC) Received: from chombo.houseloki.net (unknown [IPv6:2601:7:16c0:b50:21c:c0ff:fe7f:96ee]) by yoshi.bluerosetech.com (Postfix) with ESMTPSA id D8BF5E6079; Wed, 8 Jan 2014 13:09:14 -0800 (PST) Received: from [10.26.25.70] (c-76-115-19-22.hsd1.or.comcast.net [76.115.19.22]) by chombo.houseloki.net (Postfix) with ESMTPSA id E34369AB; Wed, 8 Jan 2014 13:09:01 -0800 (PST) Message-ID: <52CDBE74.6040702@bluerosetech.com> Date: Wed, 08 Jan 2014 13:09:08 -0800 From: Darren Pilgrim User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-fs , freebsd-questions Subject: Re: zfs upgrade hang upgrading from v3 to v5 References: <52C89140.5040700@bluerosetech.com> In-Reply-To: <52C89140.5040700@bluerosetech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Jan 2014 21:09:21 -0000 On 1/4/2014 2:54 PM, Darren Pilgrim wrote: > Later today I'll try setting a > mountpoint on it see if the upgrade will succeed then. Well, later that day didn't happen, but this morning did. To recap: When I upgraded the system from 8.3 to 9.2, I upgraded the zfs pool to feature flags and all filesystems to version 5. Everything upgraded fine, except z0, the base filesystem in the pool. z0 is the only filesystem with mountpoint=none. When upgrading z0, zfs upgrade hangs in tx->tx_sync_done_cv. The rest of the system apparently hangs on disk I/O to an extent requiring a hard reboot (NMI reset). Setting a mountpoint made the upgrade work: # zfs get mountpoint z0 NAME PROPERTY VALUE SOURCE z0 mountpoint none local # mkdir /z0 && zfs set mountpoint=/z0 z0 # zfs list z0 NAME USED AVAIL REFER MOUNTPOINT z0 84.3G 361G 30K /z0 # zfs upgrade z0 1 filesystems upgraded