From owner-freebsd-stable@FreeBSD.ORG Wed Aug 9 20:15:32 2006 Return-Path: X-Original-To: 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 9ED0E16A4DE for ; Wed, 9 Aug 2006 20:15:32 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CD0E43D45 for ; Wed, 9 Aug 2006 20:15:31 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GAuSU-0007y9-VP for freebsd-stable@freebsd.org; Wed, 09 Aug 2006 22:15:18 +0200 Received: from cmung1796.cmu.carnet.hr ([193.198.135.18]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Aug 2006 22:15:18 +0200 Received: from ivoras by cmung1796.cmu.carnet.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 09 Aug 2006 22:15:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Wed, 09 Aug 2006 22:14:53 +0200 Lines: 13 Message-ID: References: <44D993AC.3090702@sh.cvut.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: cmung1796.cmu.carnet.hr User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) In-Reply-To: <44D993AC.3090702@sh.cvut.cz> Sender: news Subject: Re: GEOM stacking X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2006 20:15:32 -0000 Václav Haisman wrote: > journaled device, too. Will it overwrite the gmirror meta data and thus > break the mirror or will it somehow magically work? Does each GEOM layer > make the resulting block device one sector shorter? No, when you create a mirror device, its size will be one sector less than size_of_raw_device. So when you add another GEOM class in it, the "last sector" will be the one before the last on the physical provider, and the new size will be two sectors less than physical, etc. In other words, geoms are "nesting" in each other and each nested geom is one sector smaller than the one it's in.