Date: Sun, 09 Nov 2014 18:41:11 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 194913] New: Problem with mount_nullfs Message-ID: <bug-194913-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-194913-8>