From owner-freebsd-stable@FreeBSD.ORG Sun Aug 12 09:23:41 2012 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 E227D106566C for ; Sun, 12 Aug 2012 09:23:41 +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 3BEEB8FC08 for ; Sun, 12 Aug 2012 09:23:40 +0000 (UTC) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: gmail) by mail.xtaz.co.uk (Postfix) with ESMTPSA id 88E4ADF3794 for ; Sun, 12 Aug 2012 10:23:38 +0100 (BST) Received: by weyx56 with SMTP id x56so2268799wey.13 for ; Sun, 12 Aug 2012 02:23:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.209.87 with SMTP id r65mr388323weo.42.1344763415479; Sun, 12 Aug 2012 02:23:35 -0700 (PDT) Received: by 10.194.39.39 with HTTP; Sun, 12 Aug 2012 02:23:35 -0700 (PDT) Date: Sun, 12 Aug 2012 10:23:35 +0100 Message-ID: From: Matt Smith To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Unable to cleanly unmount root filesystem on 9.1 amd64 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: Sun, 12 Aug 2012 09:23:42 -0000 I am running the latest code which I compiled from RELENG_9_1, although I can see that RELENG_9 is pretty much identical at this point too. I'm using the amd64 architecture on an Intel Atom D525 motherboard. I'm using UFS2 with softupdates and softupdates journalling enabled. And it's mounted via glabel. It works fine except when I try and reboot or shutdown the machine I get this error: Syncing disks, vnodes remaining...7 7 2 0 0 done All buffers synced. fsync: giving up on dirty 0xfffffe0007102780: tag devfs, type VCHR usecount 1, writecount 0, refcount 2292 mountedhere 0xfffffe000000729ca00 flags (VI(0x200)) v_object 0xfffffe0005101910 ref 0 pages 23509 lock type devfs: EXCL by thread 0xfffffe00018fe08e0 (pid 1) dev label/root umount of / failed (35) Then when the box comes back up again it detects that / was not unmounted cleanly and recovers from journal before marking it clean once more. My fstab: /dev/label/root / ufs rw 1 1 /dev/label/swap none swap sw 0 0 My gpart: => 34 1250263661 ada0 GPT (596G) 34 1024 1 freebsd-boot (512k) 1058 990 - free - (495k) 2048 1228931072 2 freebsd-ufs (586G) 1228933120 21330575 3 freebsd-swap (10G) I have also tried changing this to /dev/ada0p2 in case it was an issue with using labels and it does the same thing. I had no problems with it unmounting from the USB install stick that I used which was 9.1-BETA1, it's only started doing this since I updated it to RELENG_9_1. I did make a custom kernel file when I did that as well, but I don't think I've taken anything important out of it. Any ideas? Regards, Matt.