From owner-freebsd-questions Sun Dec 26 17:40:13 1999 Delivered-To: freebsd-questions@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 2E81B14A1E for ; Sun, 26 Dec 1999 17:40:09 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA42286; Mon, 27 Dec 1999 12:09:59 +1030 (CST) Date: Mon, 27 Dec 1999 12:09:59 +1030 From: Greg Lehey To: Tomaz Borstnar Cc: freebsd-questions@FreeBSD.ORG Subject: Re: vinum in FreeBSD 3.4, concat-ed plexes and reviving state Message-ID: <19991227120959.T1316@freebie.lemis.com> References: <4.2.2.19991227014323.00cb75c0@193.189.189.100> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <4.2.2.19991227014323.00cb75c0@193.189.189.100> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 27 December 1999 at 1:48:20 -0100, Tomaz Borstnar wrote: > Hello! > > Have FreeBSD 3.4 and 2 identical IDE disks - each on their own channel and > vinum set for mirroring: > > Plex var.p0: Size: 2097152000 bytes (2000 MB) [verbose plex config omitted] > ------------- > Config: > > # > # Our drives > drive disk1 device /dev/wd0s1e > drive disk2 device /dev/wd2s1e > # > volume var If you want them to come up immediately, ignoring the obvious fact that the data on the subdisks is not consistent, use the 'setupstate' keyword here: volume var setupstate Read vinum(4) for a longer discussion. > Well, everything works, but 'vinum l -V' shows that p1 plexes are > always in reviving state - even after 2 days! How long does it take > to sync the contents? It would probably take an hour or two. The problem here is that you need to start the revive manually, and the state doesn't change. The l -V output will also show that the revive pointer is set to 0. Maybe I need a better name than 'reviving'. 'needs reviving' might be better, but it looks funny in messages like vinum: var.p0 is needs reviving. If anybody has a good suggestion about how to make this less ambiguous, I'm all ears. > Is this correct setup for raid-1 with identical disks? Looks good enough to me, modulo the setupstate keyword. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message