From owner-freebsd-current@FreeBSD.ORG Sun Apr 24 19:09:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB19F16A4CE; Sun, 24 Apr 2005 19:09:17 +0000 (GMT) Received: from mx.toxahost.ru (ns.toxahost.ru [62.89.204.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685C543D54; Sun, 24 Apr 2005 19:09:17 +0000 (GMT) (envelope-from toxa@toxahost.ru) Received: from localhost (laptoxa.toxa.lan [192.168.1.3]) by mx.toxahost.ru (Toxa) with ESMTP id 1FA9B122; Sun, 24 Apr 2005 23:09:16 +0400 (MSD) Date: Sun, 24 Apr 2005 23:09:12 +0400 From: Toxa To: freebsd-current@freebsd.org, freebsd-geom@freebsd.org X-Comment-To: "Anton A. Karpov" Message-ID: <20050424190912.GA6743@laptoxa.toxa.lan> Mail-Followup-To: freebsd-current@freebsd.org, freebsd-geom@freebsd.org, Pawel Jakub Dawidek References: <20050424022434.GA3384@laptoxa.toxa.lan> <20050424094343.GA837@darkness.comp.waw.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20050424094343.GA837@darkness.comp.waw.pl> User-Agent: Outluck Express 1.5.6i for MS-DOS 6.22-SMP X-Mailer: See User-Agent above :) X-Operating-System: MS-DOS 6.22-CURRENT on Sony VAIO laptop X-PGP-Public-Key: http://toxahost.ru/gpg/pubkey.asc X-Useless-Header: Do Androids Dream of Electric Sheep? cc: Pawel Jakub Dawidek Subject: Re: gmirror: Not all disks connected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Apr 2005 19:09:17 -0000 On Sun, Apr 24, 2005 at 11:43:43AM +0200, Pawel Jakub Dawidek wrote: > Please read description of 'forget' subcommand. Well, FYI, the problem *I THINK* was in the fact disks are not equal in size (ad1 is 3 sectors bigger): ad0: 38203MB [77619/16/63] at ata0-master UDMA100 ad1: 38204MB [77622/16/63] at ata0-slave UDMA100 In this case, fresh system was installed onto ad0, gm0 was created on ad1, when synchronise with added ad0 (as described in your step-by-step guide). The first synchronisation process (after addinbg ad0 into gm0) *was ok*, but after reboot, *I THINK*, gmirror discovered ad0 is less size than ad1 and refused to include it into gm0. Is this a bug or feature? The problem was solved by forget'ing gm0, creating gm1 on ad0, whet rebooting and adding ad1 (wthic is bigger than ad0) into it. Now everything seems to work ok... Thanks for the gmirror.