The null fs layer does not release the space of a removed file.

[Sven Kirmess <Sven.Kirmess@gmx.net>]

I have a strange problem with mount_null on my Intel box. Whenever I
remove a file the space is made free again. A umount of the null mount
point
(which may fail because I'm in the directory) frees the space. Is that
a known
problem or should I make a bug report?

Sven

$ uname -a
OpenBSD garak 3.1 GENERIC+RAID#0 i386
$ pwd
/home/ski
$ df -k .
Filesystem   1K-blocks     Used    Avail Capacity  Mounted on
/export/home  10076064  7635501  1936760    80%    /home
$ ls -l testfile
-rw-r-----  1 ski  users  46432256 May  6 21:45 testfile
$ cp testfile testcopy
$ df -k .
Filesystem   1K-blocks     Used    Avail Capacity  Mounted on
/export/home  10076064  7680876  1891385    80%    /home
$ rm testcopy
$ df -k .
Filesystem   1K-blocks     Used    Avail Capacity  Mounted on
/export/home  10076064  7680876  1891385    80%    /home
$ su root
Password:
garak# umount /home
umount: /home: Device busy
garak# exit
$ df -k .
Filesystem   1K-blocks     Used    Avail Capacity  Mounted on
/export/home  10076064  7635500  1936761    80%    /home
$