From owner-freebsd-stable@FreeBSD.ORG Mon Aug 27 14:09:02 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 587DE106566B for ; Mon, 27 Aug 2012 14:09:02 +0000 (UTC) (envelope-from matt@xtaz.co.uk) Received: from mail.xtaz.co.uk (tao.xtaz.co.uk [IPv6:2a01:348:294::1]) by mx1.freebsd.org (Postfix) with ESMTP id 0BEEF8FC08 for ; Mon, 27 Aug 2012 14:09:02 +0000 (UTC) Received: from mail.xtaz.co.uk (tao.xtaz.co.uk [IPv6:2a01:348:294::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.xtaz.co.uk (Postfix) with ESMTPS id A78B2DEE7A7; Mon, 27 Aug 2012 15:09:00 +0100 (BST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 Aug 2012 15:09:00 +0100 From: Matt Smith To: Warren Block In-Reply-To: References: <2d4dfcb2637f4d0e9671899538b603d9@xtaz.co.uk> <67DFAA78-A9A2-49F9-9C29-CA5653ECE3C0@lassitu.de> <20120827172650.7e6a7685@AMD620.ovitrap.com> Message-ID: <78f8335e54e04f158609f0382afb8d4d@xtaz.co.uk> X-Sender: matt@xtaz.co.uk User-Agent: Roundcube Webmail/0.8.1 Cc: Erich Dollansky , freebsd-stable@freebsd.org, Stefan Bethke Subject: Re: 9.1 RELENG_9 Unable to cleanly dismount root partition on shutdown 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: Mon, 27 Aug 2012 14:09:02 -0000 On 2012-08-27 14:56, Warren Block wrote: > > Stefan called it. The newfs is done on /dev/gpt/gptroot, no problem > there. But when glabel writes to /dev/ada0p2--which is > /dev/gpt/gptroot, same thing, it overwrites the last block. And then > the filesystem is mounted with the glabel device, which is actually > one block smaller than the filesystem expects. > > Could be either the filesystem or GEOM that's causing the failure at > shutdown. > > Happily, those glabels aren't accomplishing anything useful and can > be skipped. Removing the glabels and changing the devices in fstab > might be enough. A more cautious approach would be to back up, > newfs, > skip the glabel step, and then change the devices in fstab. As I said on a previous mail I did boot it with a USB stick and cleared the glabel metadata and altered the fstab to point to both the GPT labels and the raw UFS device and I still get the issue. So am I right in thinking then that this has caused irreparable damage and the only way I can fix this now is to newfs the filesystem again, this time just using GPT labels and not using glabel at all? This is the first time I've ever done a manually partitioned installation with GPT and alignment, previously I've only ever used sysinstall with non-aligned MBR installations, so it was a bit of a learning curve. If I do have to newfs it again then I want to be sure that I'm doing the correct things so that I don't find myself with any other issues. So does the rest of what I did look fine? If it is clearly my own fault then the PR can obviously be closed and chalked up to learning!