linux-kernel - 2.6.38.3 leaking disk space of files created via NFS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <pan.2011.04.15.16.40.43.665250@googlemail.com>
Date:	Fri, 15 Apr 2011 18:40:43 +0200
From:	"Holger Hoffstaette" <holger.hoffstaette@...glemail.com>
To:	linux-kernel@...r.kernel.org
Subject: 2.6.38.3 leaking disk space of files created via NFS

It seems that 2.6.38.3 is still having pretty severe problems with NFS.
Files that were created/written (or only read?) via NFS can be deleted
from the server (after unmounting the client), but the disk space is not
freed. More precisely it's Gentoo's /usr/portage/distfiles on ext4 and
clients save downloaded package tarballs there.

There are no stale .nfsXX files or open file handles; the disk space is
returned after a reboot of the server, which is obviously not really an
option. I do get a message about deleted orphan inodes on reboot.

Is this a known problem? Sorry if this is a bit vague but I can't
constantly reboot the server for experiments. Anyone else who can observe
this problem?

thanks,
Holger

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/