Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Aug 2005 09:28:39 GMT
From:      soc-cjones <soc-cjones@FreeBSD.org>
To:        Perforce Change Reviews <perforce@freebsd.org>
Subject:   PERFORCE change 82750 for review
Message-ID:  <200508290928.j7T9Sdbe032552@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=82750

Change 82750 by soc-cjones@soc-cjones_ishtar on 2005/08/29 09:28:23

	Update for beta 1.

Affected files ...

.. //depot/projects/soc2005/gvinum/README#3 edit

Differences ...

==== //depot/projects/soc2005/gvinum/README#3 (text+ko) ====

@@ -1,9 +1,9 @@
-gvinum move / rename, alpha 2				19 August 2005
+gvinum move / rename, beta 1				29 August 2005
 =============================
 
 Instructions:
 
-  * Fetch http://www.ualberta.ca/~cdjones/geom_vinum_move_rename_alpha2.tgz
+  * Fetch http://www.ualberta.ca/~cdjones/geom_vinum_move_rename_beta1.tgz
 
   * Unpack it somewhere safe and out of the way.
 
@@ -28,10 +28,8 @@
   * This'll spam your console with debugging output.  I prefer to think of
     this as a feature. ;)
 
-  * syncing a volume where one plex's sd has been moved dies, because 
-    the new sd's consumer is NULL.
-
   * gvinum move will lose data when you have a striped (as opposed to
-    mirrored) configuration and you move a subdisk.
+    mirrored) configuration and you move a subdisk.  This is intended.
 
-  * geom providers are not renamed after a gvinum rename
+  * device names in /dev/gvinums are not renamed after a gvinum rename.  
+    This is a GEOM issue.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200508290928.j7T9Sdbe032552>