[Bug 178238] [nullfs] nullfs don't release i-nodes on unlink.

[bugzilla-noreply at freebsd.org]

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

noah.bergbauer at tum.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |noah.bergbauer at tum.de

--- Comment #2 from noah.bergbauer at 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=10240 tmptestbed /testbed/tmpmnt/

# test 1
mount_nullfs /testbed/tmpmnt/ /testbed/nullmnt/
df -hi | grep testbed
dd if=/dev/zero of=nullmnt/testfile # to fill up the tmpfs
df -hi | grep testbed # the filesystem is now full
rm nullmnt/testfile 
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 unmounted

# test 2: nocache
mount_nullfs -o nocache /testbed/tmpmnt/ /testbed/nullmnt/
df -hi | grep testbed
dd if=/dev/zero of=nullmnt/testfile
rm nullmnt/testfile 
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 found
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.

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