From owner-freebsd-fs@FreeBSD.ORG Sun Sep 15 14:16:03 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A51917D9; Sun, 15 Sep 2013 14:16:03 +0000 (UTC) (envelope-from jdavidlists@gmail.com) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 640B023BB; Sun, 15 Sep 2013 14:16:03 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id as1so5848168iec.35 for ; Sun, 15 Sep 2013 07:16:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ZjKB2FGfJYgqGVGEQPVWmgT8hAIk5/BSoNHWMThtkPA=; b=LIR0cKffOZJ13T8CjBNAFNnSom83RkNk5t4sM0XC0VtBlL0S6nohRdXE1o/dz9s8lV 0np7WHwWxqr8npxHgbSjbMjUIwKe2hYOrRgLV8wobHLkzXGjn/6+Frskt6F4umgySieg pZcoELZSepXrUQ3I5EJwomqCdU0Loq9dCvlbuuPnAT8vKMYlhje454JOIeHLMw4eLLTz puOIGtP8le3dXHfA9/opxAz1w4esdyZRx55BX/Zk4WqS+hrrsjQpRMlkzSM8vbZgGu9H IndDprt8SmZpXIxjFK3GTDa/Eqm9QX8YR5WRpOZejkGL/AIadJ2c84X9KpspwwFQPsp7 yCdg== MIME-Version: 1.0 X-Received: by 10.50.66.101 with SMTP id e5mr4805324igt.26.1379254562451; Sun, 15 Sep 2013 07:16:02 -0700 (PDT) Sender: jdavidlists@gmail.com Received: by 10.43.157.8 with HTTP; Sun, 15 Sep 2013 07:16:02 -0700 (PDT) In-Reply-To: <52331179.4030201@FreeBSD.org> References: <523310E2.4050702@FreeBSD.org> <52331179.4030201@FreeBSD.org> Date: Sun, 15 Sep 2013 10:16:02 -0400 X-Google-Sender-Auth: vhrFkWX812s-mLA2bKILTXrVHto Message-ID: Subject: Re: zfs_enable vs zfs_load in loader.conf (but neither works) From: J David To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-fs@freebsd.org" , freebsd-stable X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Sep 2013 14:16:03 -0000 Thanks very much for the info Andriy. On Fri, Sep 13, 2013 at 9:22 AM, Andriy Gapon wrote: > Another piece of information is that neither mountpoint nor canmount property > affects ZFS root mounting. It is mountpoint=legacy that boots on this machine and mountpoint=/ that can't find init, with no other changes. So clearly under some obscure edge case, this is not strictly correct. Did your test include zpool root != filesystem root? Because as you describe one possible cause of the problem is mounting the wrong filesystem as root, one wonders if somehow with the mountpoint=/ setting the zpool root (which has no files at all) is incorrectly being chosen as fsroot with mountpoint=/ on data/root. I.e. perhaps somewhere in the code is looking for "legacy" (or skipping anything with a mountpoint set) and defaulting back to the zpool root if it is not found? Unfortunately there is no way I know of to check and see what the root filesystem turned out to be after the failure to find init. That would reduce speculation about what is happening quite a bit. Can the kernel debugger extract this info? If it matters, the pools in question are fairly complex, not just throwing everything possible on one drive. Example: NAME STATE READ WRITE CKSUM data ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 da0p2 ONLINE 0 0 0 da4p2 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 da1p2 ONLINE 0 0 0 da5p2 ONLINE 0 0 0 mirror-2 ONLINE 0 0 0 da2p2 ONLINE 0 0 0 da6p2 ONLINE 0 0 0 mirror-3 ONLINE 0 0 0 da3p2 ONLINE 0 0 0 da7p2 ONLINE 0 0 0 logs ada0p2 ONLINE 0 0 0 cache ada1p2 ONLINE 0 0 0 The boot order for that system begins at either ada0 or da0, not sure which without checking the BIOS. Thanks!