From owner-freebsd-bugs@FreeBSD.ORG  Sun Nov  9 18:41:11 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id E9C6C4E7
 for <freebsd-bugs@FreeBSD.org>; Sun,  9 Nov 2014 18:41:11 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D262394D
 for <freebsd-bugs@FreeBSD.org>; Sun,  9 Nov 2014 18:41:11 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sA9IfB7k074323
 for <freebsd-bugs@FreeBSD.org>; Sun, 9 Nov 2014 18:41:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194913] New: Problem with mount_nullfs
Date: Sun, 09 Nov 2014 18:41:11 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: dawid.piotrowski@gmail.com
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform
 op_sys bug_status bug_severity priority component assigned_to reporter
Message-ID: <bug-194913-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Nov 2014 18:41:12 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194913

            Bug ID: 194913
           Summary: Problem with mount_nullfs
           Product: Base System
           Version: 10.0-RELEASE
          Hardware: amd64
                OS: Any
            Status: Needs Triage
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: dawid.piotrowski@gmail.com

I discoverd an issue with mount_nullfs binary. When phisical drive eg.
/dev/da0p2 is mounted to / and i mount_nullfs eg. /home/user /mnt (or any other
place), there is a problem with updating space in df -h. What i know, when i do
dd if=/dev/zero of=bigfile bs=1024 count=5120000 in /mnt and do df -h i get
properly announced space (-500mb of free space), but when i deleted bigfile in
/mnt that 500MB wont back to Avail neither on nullfs mount or in phisical drive
mount. What helps is unmounting nullfs and then space info get updated on
phisical drive mount. 
I did a tests on 2 diferent machines, both with latest stable FreeBSD. If
needed i can provide additional info.

-- 
You are receiving this mail because:
You are the assignee for the bug.