From owner-freebsd-stable@FreeBSD.ORG Sat Oct 2 15:20:00 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 189341065670 for ; Sat, 2 Oct 2010 15:20:00 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (unknown [IPv6:2a01:348:0:15:5d59:5c40:0:1]) by mx1.freebsd.org (Postfix) with ESMTP id CBA9E8FC0C for ; Sat, 2 Oct 2010 15:19:59 +0000 (UTC) Received: from muon.cran.org.uk (localhost [127.0.0.1]) by muon.cran.org.uk (Postfix) with ESMTP id 245C5E63CD; Sat, 2 Oct 2010 16:19:59 +0100 (BST) Received: from unknown (client-82-31-11-222.midd.adsl.virginmedia.com [82.31.11.222]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA; Sat, 2 Oct 2010 16:19:58 +0100 (BST) Date: Sat, 2 Oct 2010 16:19:56 +0100 From: Bruce Cran To: Matthew Seaman Message-ID: <20101002161956.00007257@unknown> In-Reply-To: <4CA74C18.2020405@infracaninophile.co.uk> References: <1C68D21A-9539-473D-AEDB-9A8CCE4956F1@pean.org> <4CA73215.9030908@ksu.ru> <4CA74C18.2020405@infracaninophile.co.uk> X-Mailer: Claws Mail 3.7.6 (GTK+ 2.16.6; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "Marat N.Afanasyev" , stable@freebsd.org, Peter =?ISO-8859-1?Q?Ankerst=E5l?= Subject: Re: device names changes for adX. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Oct 2010 15:20:00 -0000 On Sat, 02 Oct 2010 16:13:28 +0100 Matthew Seaman wrote: > In fact, if you glabel the disks while ZFS is still active, it should > instantly recognise all the new names and update the 'zpool status' > output on the fly. Actually, that last is probably the right way to > do things -- you'll update the zpool.cache that way, which means that > ZFS will come up without any remedial action after reboot. Since glabel writes metadata to disk, won't doing this on a disk with a filesystem corrupt something? -- Bruce Cran