Date: Wed, 30 Dec 2015 15:07:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 178238] [nullfs] nullfs don't release i-nodes on unlink. Message-ID: <bug-178238-3630-OCaOvO9YrZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-178238-3630@https.bugs.freebsd.org/bugzilla/> References: <bug-178238-3630@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-178238-3630-OCaOvO9YrZ>