Bug 81778

Summary:	'gmirror label' does not attach mirror as 'gconcat label' does.
Product:	Base System	Reporter:	trasz <trasz>
Component:	kern	Assignee:	Pawel Jakub Dawidek <pjd>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	Unspecified
Hardware:	Any
OS:	Any

Description trasz 2005-06-01 20:50:01 UTC

when you do 'gconcat label' it records metadata and attaches newly configured gconcat.  'gmirror label' works differently - it only writes metadata, you still need to do 'gmirror load' for the mirror to attach.

Comment 1 Tilman Keskinoz freebsd_committer

2005-06-06 17:42:14 UTC

Responsible Changed
From-To: freebsd-bugs->pjd

over to maintainer

Comment 2 Pawel Jakub Dawidek freebsd_committer

2005-08-15 12:17:02 UTC

State Changed
From-To: open->closed

This is intented, because I wanted to allow to setup a mirror on working 
system without actually loading it, so it won't start synchronization, 
it won't try to open providers, etc. 
This is simlar in graid3. Those two classes always keep open components r1w1e1, 
so nasty things can happen when you setup and load mirror/raid3 on a working 
system where individual components are already mounted. 
Other classes like gconcat, gstripe, only open providers when needed, so can 
load modules without the risk.