From owner-freebsd-stable@FreeBSD.ORG Fri Mar 23 18:50:14 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7475106564A for ; Fri, 23 Mar 2012 18:50:14 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 0C8F48FC1B for ; Fri, 23 Mar 2012 18:50:13 +0000 (UTC) Received: by lboi15 with SMTP id i15so3591437lbo.13 for ; Fri, 23 Mar 2012 11:50:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=Rw7oZG5bVXNppdee9Vu8JmxCpOzuc6HnDsrw0F9tOxg=; b=TqMiCwlzB7HhDZ1YfqUWXaVGztAF6XmjNgwb3zKpnOqmJVHh8QWrt1CVDR/DVszXka aMMUmN1Uu3VfGYkiWdbJlbuVsfyH0vrK4aXA0+w5FpPi+S3Pm8i9FUyVG4GbpYaz6xjK 06iunXZ8GanTTCFAHphdq8S09WanuBloRp9ggQc/ncD9NCQn2xumyh0T++NDOc9ijwV2 ZUhyuud66pd0bRYenV3c1lMiBEc5bQ2aNKpRbEnwSdnEvqFjluZqucAw6moIoXze3oW5 otOLr/Y1O6VaYd7PSevRJJ6vLf/TcK0Rv3aSRmBZZEh/TRk14hm+ZINSXupwzMLfyhcf iISQ== MIME-Version: 1.0 Received: by 10.112.23.38 with SMTP id j6mr4976849lbf.15.1332528612809; Fri, 23 Mar 2012 11:50:12 -0700 (PDT) Received: by 10.112.36.135 with HTTP; Fri, 23 Mar 2012 11:50:12 -0700 (PDT) X-Originating-IP: [216.223.13.128] Date: Fri, 23 Mar 2012 14:50:12 -0400 Message-ID: From: Mark Saad To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQlFXFsbYQzGY3jN4xAA+1x5mwMsl13fU9CRBy26ajTdeOIb7nZpIrMkVKNfyuZAPwJKNHVV Subject: FreeBSD 9-STABLE can not mount root from a glabled device 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: Fri, 23 Mar 2012 18:50:14 -0000 All I upgraded two of my 7-STABLE servers to 9-STABLE today and found two foot shooters. I believe they are bugs only when you upgrade from pre 8.0-RELEASE to 9.0-RELEASE or 9-STABLE 1. On 7.x I had been using glabel to label my root filesystem slice, swap slice , and var slice . Like this glabel label rootfs /dev/da0s1a glabel label var /dev/da0s1d glabel label SWAP /dev/da0s1b Then in fstab I would have entries like this. # Device Mountpoint FStype Options Dump Pass# /dev/label/rootfs / ufs rw 1 1 /dev/label/var /var ufs rw 2 2 /dev/label/SWAP none swap sw 0 0 This has worked for me in 6.x and 7.x however upon upgrading to 9-STABLE ( from yesterday ) or 9.0-RELEASE the boot loader could not find the labeled device. I had to manually set vfs.root.mountfrom=ufs:/dev/da0s1a" or key that in when the boot process bombed out. 2. After fixing the fstabs to use the real da names I wanted to see what the boot loader would do with ufs labels. I rebooted my box into single user mode and ran this tunefs -L rootfs /dev/da0s1a tunefs -L var /dev/da0s1d Then edited the fstab to use the labeled filesystems and rebooted, much to my surprise it failed in the same way. I compared this to a new 9.0-STABLE install i did which used gpt labels that did would # Device Mountpoint FStype Options Dump Pass# /dev/label/SWAP none swap sw 0 0 /dev/gpt/rootfs / ufs rw 1 1 /dev/gpt/var /var ufs rw 2 2 /dev/gpt/data /data ufs rw 2 2 So far as I can tell the only difference is that the fresh install uses the GPT partitioning scheme where as the upgraded boxes us the older mbr/fdisk setup. Any ideas on what I can try to get past this ? I liked using /dev/label as it made the devices sort of agnostic to what filesystem or partitioning scheme was on them. -- mark saad | nonesuch@longcount.org