From owner-freebsd-bugs@FreeBSD.ORG Tue Jul 15 11:10:01 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85492106566B for ; Tue, 15 Jul 2008 11:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4B7188FC1C for ; Tue, 15 Jul 2008 11:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m6FBA1E0078968 for ; Tue, 15 Jul 2008 11:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m6FBA11j078967; Tue, 15 Jul 2008 11:10:01 GMT (envelope-from gnats) Resent-Date: Tue, 15 Jul 2008 11:10:01 GMT Resent-Message-Id: <200807151110.m6FBA11j078967@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADA6C1065672 for ; Tue, 15 Jul 2008 11:08:22 +0000 (UTC) (envelope-from zanchey@ucc.gu.uwa.edu.au) Received: from asclepius2.uwa.edu.au (asclepius2.uwa.edu.au [130.95.128.59]) by mx1.freebsd.org (Postfix) with ESMTP id 1B84F8FC0C for ; Tue, 15 Jul 2008 11:08:22 +0000 (UTC) (envelope-from zanchey@ucc.gu.uwa.edu.au) Received: from kas30pipe.localhost (localhost.localdomain [127.0.0.1]) by panacea.uwa.edu.au (Postfix) with ESMTP id 2CF5388149 for ; Tue, 15 Jul 2008 18:34:49 +0800 (WST) Received: from panacea (localhost.localdomain [127.0.0.1]) by panacea.prekas (Postfix) with SMTP id B56FC88429 for ; Tue, 15 Jul 2008 18:34:48 +0800 (WST) Received: from mooneye.ucc.gu.uwa.edu.au (mooneye.ucc.gu.uwa.edu.au [130.95.13.9]) by panacea.extinput (Postfix) with ESMTP id A469688149 for ; Tue, 15 Jul 2008 18:34:48 +0800 (WST) Received: by mooneye.ucc.gu.uwa.edu.au (Postfix, from userid 801) id BFC7D367E9; Tue, 15 Jul 2008 18:34:46 +0800 (WST) Received: from mussel.ucc.gu.uwa.edu.au (mussel.ucc.gu.uwa.edu.au [130.95.13.18]) by mooneye.ucc.gu.uwa.edu.au (Postfix) with ESMTP id 9392A36838 for ; Tue, 15 Jul 2008 18:34:46 +0800 (WST) Received: from zanchey by mussel.ucc.gu.uwa.edu.au with local (Exim 3.36 #1 (Debian)) id 1KIhrq-0002ej-00 for ; Tue, 15 Jul 2008 18:34:46 +0800 Message-Id: Date: Tue, 15 Jul 2008 18:34:46 +0800 From: " To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: kern/125632: gvinum rename does not work for drive objects X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: zanchey@ucc.gu.uwa.edu.au List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jul 2008 11:10:01 -0000 >Number: 125632 >Category: kern >Synopsis: gvinum rename does not work for drive objects >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jul 15 11:10:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: David Adam >Release: FreeBSD 7.0-RELEASE-p2 i386 >Organization: University Computer Club, UWA >Environment: System: FreeBSD blade.ucc.gu.uwa.edu.au 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed Jun 18 07:33:28 UTC 2008 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 >Description: The 'rename' command in gvinum doesn't appear to persist across reboots on drive objects in 7.0-RELEASE. I initially created three drive objects to support my RAID-5 gvinum setup, named 'r0', 'r1' and 'r2'. Straightaway, I realised that this was not the naming scheme I had intended to use, but rather than deleting and recreating them, I tried renaming to 'rA', 'rB' and 'rC'. This appeared to complete successfully, I created the appropriate volume and plex, newfs(8)ed the filesystem, and mounted it. However, on rebooting the machine (some days later) I discovered that the rename operation did not persist across a reboot. Thus, I have three drives named 'r0', 'r1' and 'r2', and a RAID-5 plex that looks for drives to attach to subdisks named 'rA', 'rB' and 'rC'. It fails to load successfully, and I am left without a running volume. No amount of booting to single user and issuing 'rename r0 rA', with or without 'saveconfig', results in a drive name change that persists across reboots. >How-To-Repeat: - Create disk 'r0' - Rename to 'rA' - If you would like things to go spang, create a plex containing rA at this point - 'saveconfig' (optional, does not affect outcome) - Reboot - `gvinum list` shows disk r0 >Fix: >Release-Note: >Audit-Trail: >Unformatted: