From owner-freebsd-stable@FreeBSD.ORG Sat Feb 19 14:47:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ABE9C16A4CE for ; Sat, 19 Feb 2005 14:47:56 +0000 (GMT) Received: from out010.verizon.net (out010pub.verizon.net [206.46.170.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DC4643D5A for ; Sat, 19 Feb 2005 14:47:56 +0000 (GMT) (envelope-from Remo.Lacho@verizon.net) Received: from pool-141-154-209-224.bos.east.verizon.net ([141.154.209.224]) by out010.verizon.netESMTP <20050219144754.VAEB3892.out010.verizon.net@pool-141-154-209-224.bos.east.verizon.net> for ; Sat, 19 Feb 2005 08:47:54 -0600 Received: from bortel.dyndns.org by bortel.dyndns.org with [XMail 1.21 ESMTP Server] ; Sat, 19 Feb 2005 09:47:52 -0500 Date: Sat, 19 Feb 2005 09:47:53 -0500 From: "Remo Lacho" To: freebsd-stable@freebsd.org Content-Type: text/plain; charset="ISO-8859-9" Message-ID: X-Authentication-Info: Submitted using SMTP AUTH at out010.verizon.net from [141.154.209.224] at Sat, 19 Feb 2005 08:47:54 -0600 Subject: How to remove vestigial gmirror device? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Remo.Lacho@verizon.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Feb 2005 14:47:56 -0000 Installed 5.3-Stable from the February ISO Snapshot on an old Pentium Pro 600MH ATX box with 256MB memory and two WD UDMA33 6.4GB drives. After several false starts with GMirror (guided by Ralf S. Engelschal's excellent How-To ) the system is now stable and has survived many kernel recompiles without incident. One problem, one of the original test GMirror devices refused to go away. It did not respond to the "remove" or "forget" parameters. The "deactivate" parameter seemed to do the trick, however, upon boot-up the following message is generated: "GEOM_MIRROR: Device gmusr: provider ad4 marked as inactive, skipping." The "list" parameter does not list the gmusr device as being active. When "gmirror activate gmusr ad4" is invoked the response is: "Cannot write metadata from ad4: Operation not permitted. Not fully done." Although the vestigial device does not seem to cause any trouble, it is annoying to get the message at boot-up. I there a configuration file that can be edited or a specific disk sector where the device entry can be deleted with a disk editor? If not, any other way to remove the device permanently other than a system reinstall. Thank you. -- Remo