From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 29 14:52:43 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D60FE16A4CE; Mon, 29 Nov 2004 14:52:43 +0000 (GMT) Received: from minerva.int.gov.br (nat.int.gov.br [200.20.196.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9344443D39; Mon, 29 Nov 2004 14:52:42 +0000 (GMT) (envelope-from jonny@jonny.eng.br) Received: from [10.0.8.17] (dinf-02 [10.0.8.17]) by minerva.int.gov.br (Postfix) with ESMTP id 364B9BE56A; Mon, 29 Nov 2004 12:52:40 -0200 (BRDT) Message-ID: <41AB37B8.7060303@jonny.eng.br> Date: Mon, 29 Nov 2004 12:52:40 -0200 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <41A4FD60.4050501@jonny.eng.br> <20041125224547.GB7232@darkness.comp.waw.pl> <41A6B76F.4020101@jonny.eng.br> <20041126082340.GC7232@darkness.comp.waw.pl> <41A78A47.3050309@jonny.eng.br> <20041128202759.GF7232@darkness.comp.waw.pl> In-Reply-To: <20041128202759.GF7232@darkness.comp.waw.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org Subject: Re: Hand on gmirror (Was: Re: gmirror bugs, how many?) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 14:52:43 -0000 Pawel Jakub Dawidek wrote: > Not working 'unload' command is because of bug in GEOM. Now, to avoid > deadlock you get an error (ENXIO), but mirror will be destroyed. > The next 'unload' should be ok. To avoid those errors, you should first > stop all mirrors (unsing 'stop' command) and then unload kernel module. I thought unload did a stop before. > BTW. There is no 'reload' command. I know, I meant redoing the load command. > +> Indeed, the -h option is what I wanted and the "bug" is in the > +> manual. What would happen if I change the disc ID in this case? > > Your disk will not be detected as a mirror component, because hardcoded > name is different. Oops. Is there a check for that? For example, let's say that ad0s1 got renamed to ad1s1, and hardcoded a reference to ad0s1. In this case, there is a disk called ad0s1 in the system. Is gmirror smart enough in this case? > +> sigesc::root jcmendes [553] disklabel mirror/vol0 > +> # /dev/mirror/vol0: > +> 8 partitions: > +> # size offset fstype [fsize bsize bps/cpg] > +> a: 16498864 16 unused 0 0 > +> c: 16498880 0 unused 0 0 # "raw" part, > +> don't edit > +> sigesc::root jcmendes [554] > +> > +> Seems good until now. Except for the offset 16 of the "a" partition. > +> Is this necessary? The man page says that the only sector reserved > +> for metadata is the provider's last one. > > Ehh, "blame" disklabel(8). First 16 sectors are reserved for boot code. And why this does not happen with ad0s1, etc?