From owner-freebsd-fs@freebsd.org Wed Dec 30 15:07:56 2015 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0491BA55C39 for ; Wed, 30 Dec 2015 15:07:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) 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 D0C0C1CE5 for ; Wed, 30 Dec 2015 15:07:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBUF7tvQ022303 for ; Wed, 30 Dec 2015 15:07:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 178238] [nullfs] nullfs don't release i-nodes on unlink. Date: Wed, 30 Dec 2015 15:07:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: noah.bergbauer@tum.de X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Dec 2015 15:07:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D178238 noah.bergbauer@tum.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noah.bergbauer@tum.de --- Comment #2 from noah.bergbauer@tum.de --- This PR is tagged 9.1-STABLE, but I just rediscovered this issue on 10.2-RELEASE. Easiest repro I could find: # preparation mkdir /testbed cd /testbed mkdir tmpmnt nullmnt mount -t tmpfs -o rw,size=3D10240 tmptestbed /testbed/tmpmnt/ # test 1 mount_nullfs /testbed/tmpmnt/ /testbed/nullmnt/ df -hi | grep testbed dd if=3D/dev/zero of=3Dnullmnt/testfile # to fill up the tmpfs df -hi | grep testbed # the filesystem is now full rm nullmnt/testfile=20 df -hi | grep testbed # bug: the filesystem is still full umount /testbed/nullmnt df -hi | grep testbed # the inode is released only once the nullfs is unmou= nted # test 2: nocache mount_nullfs -o nocache /testbed/tmpmnt/ /testbed/nullmnt/ df -hi | grep testbed dd if=3D/dev/zero of=3Dnullmnt/testfile rm nullmnt/testfile=20 df -hi | grep testbed # everything is working properly here umount /testbed/nullmnt So a standard nullfs mount is unusable for long-term operation. I've only f= ound out about the nocache option from an old mailing list post related to this = PR, so after 2.5 years without a fix a note about this workaround on the manpage would be great. --=20 You are receiving this mail because: You are the assignee for the bug.=