From owner-freebsd-current@FreeBSD.ORG  Sun Dec 12 11:58:56 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2984816A4CE
	for <current@freebsd.org>; Sun, 12 Dec 2004 11:58:56 +0000 (GMT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 82AF043D5E
	for <current@freebsd.org>; Sun, 12 Dec 2004 11:58:55 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBCBwqf7012574;
	Sun, 12 Dec 2004 12:58:52 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Aurelien Nephtali <aurelien.nephtali@wanadoo.fr>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sun, 12 Dec 2004 12:47:50 +0100."
             <41BC2FE6.10204@wanadoo.fr> 
Date: Sun, 12 Dec 2004 12:58:52 +0100
Message-ID: <12573.1102852732@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: current@freebsd.org
Subject: Re: [TEST] NTFS patch 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Dec 2004 11:58:56 -0000

In message <41BC2FE6.10204@wanadoo.fr>, Aurelien Nephtali writes:
>Poul-Henning Kamp wrote:
>> Here is a combined patch for the two problems that's been
>> reported against NTFS after my mount changes.
>> 
>> Please test & report.
>> 
>
>It works fine for me! Thanks!
>
>I have another problem which could be triggered by your mount changes :
>
>Even if I do a clean reboot/halt, at next boot I got:
>
>Starting file system checks:
>/dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
>/dev/ad0s2a: clean, 19040 free (1088 frags, 2244 blocks, 1.7% fragmentation)
>/dev/ad0s2f: DEFER FOR BACKGROUND CHECKING
>/dev/ad0s2g: DEFER FOR BACKGROUND CHECKING
>/dev/ad0s2e: DEFER FOR BACKGROUND CHECKING
>WARNING: /tmp was not properly dismounted
>WARNING: /usr was not properly dismounted
>WARNING: /var was not properly dismounted
>
>or maybe it's not linked to your changes but...

That's just "normal" dirty filesystems.  It should fix itself once
bgfsck completes.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.