From owner-freebsd-geom@FreeBSD.ORG Sat Oct 7 22:23:39 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E9E116A403 for ; Sat, 7 Oct 2006 22:23:39 +0000 (UTC) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6BCB43D4C for ; Sat, 7 Oct 2006 22:23:38 +0000 (GMT) (envelope-from gcubfg-freebsd-geom@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GWKZm-0001fx-Bn for freebsd-geom@freebsd.org; Sun, 08 Oct 2006 00:23:22 +0200 Received: from 89-172-40-28.adsl.net.t-com.hr ([89.172.40.28]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Oct 2006 00:23:22 +0200 Received: from ivoras by 89-172-40-28.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Oct 2006 00:23:22 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-geom@freebsd.org From: Ivan Voras Date: Sun, 08 Oct 2006 00:23:13 +0200 Lines: 9 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-40-28.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: Sender: news Subject: Re: gmirror, removing disk and mounting gives strange error X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Oct 2006 22:23:39 -0000 Johan Ström wrote: > Okay, so the FS might not be clean since I removed the disk while the FS > was mounted.. But why does it report gm1s1g?? thats the mountpoint of my > gm1 mirror (or rather the s1g on the gm1 mirror).. Confusing ;) UFS records the mountpoint where the file system was last mounted. I've seen fsck use this information when reporting error messages, so this may be the reason.