From owner-freebsd-stable@FreeBSD.ORG  Sun Nov  7 09:42:05 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
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 B882716A4CE
	for <freebsd-stable@freebsd.org>;
	Sun,  7 Nov 2004 09:42:05 +0000 (GMT)
Received: from smart.eusc.inter.net (smart.eusc.inter.net [213.73.101.5])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7701943D1D
	for <freebsd-stable@freebsd.org>;
	Sun,  7 Nov 2004 09:42:05 +0000 (GMT)	(envelope-from msch@snafu.de)
Received: from dial-76-134.de.inter.net ([213.73.76.134]
	helo=current.best-eng.de)
	by smart.eusc.inter.net with esmtp (Exim 3.36 #4)
	id 1CQjYi-0002Dq-00; Sun, 07 Nov 2004 10:42:04 +0100
Received: from current.best-eng.de (localhost.best-eng.de [127.0.0.1])
	by current.best-eng.de (8.13.1/8.13.1) with ESMTP id iA79g3jS001306;
	Sun, 7 Nov 2004 10:42:03 +0100 (CET)
	(envelope-from msch@snafu.de)
Received: from localhost (localhost [[UNIX: localhost]])
	by current.best-eng.de (8.13.1/8.13.1/Submit) id iA79g36Z001305;
	Sun, 7 Nov 2004 10:42:03 +0100 (CET)
	(envelope-from msch@snafu.de)
X-Authentication-Warning: current.best-eng.de: matthias set sender to
	msch@snafu.de using -f
From: Matthias Schuendehuette <msch@snafu.de>
Organization: Micro$oft-free Zone
To: secmgr <security@jim-liesl.org>
Date: Sun, 7 Nov 2004 10:42:03 +0100
User-Agent: KMail/1.7
References: <02f201c4ba91$f9f95db0$33017f80@psique>
	<200411061217.06061.msch@snafu.de> <1099805401.4420.4.camel@emperor>
In-Reply-To: <1099805401.4420.4.camel@emperor>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200411071042.03382.msch@snafu.de>
cc: freebsd-stable@freebsd.org
Subject: Re: freebsd 5.3 have any problem with vinum ?
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: msch@snafu.de
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Nov 2004 09:42:05 -0000

Am Sonntag, 7. November 2004 06:30 schrieb secmgr:
> On Sat, 2004-11-06 at 04:16, Matthias Schuendehuette wrote:
> > Did you try to simply 'start' the plex? This works for
> > initialisation of a newly created RAID5-Plex as well as for
> > recalculating parity informations on a degraded RAID5-Plex.
>
> I did a gvinum start.

No, that's not what I meant.

'gvinum start' loads the kernel module which in turn searches for 
vinum-GEOMs and loads the configuration data. It doesn't change the 
state of any gvinum item.

Try 'gvinum start <plex-name>' or within gvinum(8):

gvinum> start <plexname>

This (as far as I investigated :-)

a) initializes a newly created RAID5-plex    or

b) recalculates parity informations on a degraded RAID5-plex with
   a new replaced subdisk.

So, a 'gvinum start raid5.p0' initializes my RAID5-plex if newly 
created. You can monitor the initialization process with subsequent 
'gvinum list' commands.

If you degrade a RAID5-plex with 'camcontrol stop <diskname>' (in case 
of SCSI-Disks) and 'repair' it afterwards with 'camcontrol start 
<diskname>', the 'gvinum start raid5.p0' (my volume here is called 
'raid5') command recalculates the parity and revives the subdisk which 
was on disk <diskname>.
-- 
Ciao/BSD - Matthias

Matthias Schuendehuette <msch [at] snafu.de>, Berlin (Germany)
PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F