Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jul 2008 18:34:46 +0800
From:      "<zanchey"@ucc.gu.uwa.edu.au
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   kern/125632: gvinum rename does not work for drive objects
Message-ID:  <E1KIhrq-0002ej-00@mussel.ucc.gu.uwa.edu.au>
Resent-Message-ID: <200807151110.m6FBA11j078967@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>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 <zanchey@ucc.gu.uwa.edu.au>
>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:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1KIhrq-0002ej-00>