From owner-freebsd-stable@FreeBSD.ORG Wed Apr 29 07:35:03 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20BD51065675; Wed, 29 Apr 2009 07:35:03 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id EC9288FC15; Wed, 29 Apr 2009 07:35:01 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id KAA21275; Wed, 29 Apr 2009 10:34:59 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1] helo=edge.pp.kiev.ua) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1Lz4Jm-000Hlh-RS; Wed, 29 Apr 2009 10:34:58 +0300 Message-ID: <49F80321.6030305@icyb.net.ua> Date: Wed, 29 Apr 2009 10:34:57 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.21 (X11/20090406) MIME-Version: 1.0 To: Ivan Voras References: <49F5DE4B.2070702@icyb.net.ua> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, freebsd-geom@freebsd.org Subject: Re: fsck, glabel and sudden parallelism 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, 29 Apr 2009 07:35:03 -0000 on 28/04/2009 14:34 Ivan Voras said the following: > Andriy Gapon wrote: >> So I recently switched one system to have only (g)labels instead of "raw" device >> names in fstab and noticed that now initial (preen) fsck is performed in parallel >> on couple of filesystems where before it used to be sequential. >> >> Here is a lengthy quote from fsck(8): [snip] >>> The disk drive containing each file system is inferred from the shortest >>> prefix of the device name that ends in a digit; the remaining characters >>> are assumed to be the partition and slice designators. >> I think it is highly desirable that fsck knows which filesystems reside on the >> same disk regardless of how they are referred to. >> I think that the simple string matching described above is not sufficient these days. >> Is there an easy geom way to query this info? > > Yes, contents of kern.geom.confxml could be used to walk the tree of > GEOM devices and find what drive they are physically on. It seems that the less interesting part is already done - geom_gettree() from libgeom, the more interesting part is some logic for directed graph (geom "mesh") navigation. Marcel, I seem to recall that there was a conversation about making fsck more geom aware (it was in context of inferring fs type from disklabel). Do you have any work in progress in this area? -- Andriy Gapon