Date: Sun, 16 May 2004 22:42:40 -0500 From: Eric Anderson <anderson@centtech.com> To: Dan Nelson <dnelson@allantgroup.com> Cc: freebsd-questions@freebsd.org Subject: Re: Disk full / NFS, df, and du Message-ID: <40A834B0.60806@centtech.com> In-Reply-To: <20040517032438.GE80376@dan.emsphone.com> References: <40A82BAB.7030005@centtech.com> <20040517032438.GE80376@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson wrote: >In the last episode (May 16), Eric Anderson said: > > >>I have a few large NFS file servers, holding about 1Tb of diskspace >>each. I break those logical disks (it's on a hardware RAID) into >>partitions, and share them. My users fill up the partitions often >>enough, and when they do, they rm entire directory trees to free the >>space. They use du to determine how much space is in a directory and >>how much they are hogging. >> >>The problem I'm having is, after they do the rm's, it doesn't free the >>disk space. df shows it still being used, but du claims their >>directories are empty. >> >>If I reboot the file server, the space magically appears. >> >>I was thinking that it was because a process was using the data, or >>directories the data was removed from, so the blocks weren't actually >>freed, but that seems a little odd to me, since they claim (and >>different users have the same issues, and make the same claims) that >>nothing should be touching those areas at all. >> >>How do I get FreeBSD to release those blocks without rebooting? >> >> > >Does a du on server itself show files? How about "lsof +L1"? The NFS >protocol doesn't allow clients to unlink files they have open, so >FreeBSD clients (at least) rename open files that are unlinked to >.nfs##### until the last process closes the file, and then they delete >it. If you've got unlinked files held open, it's got to be on the >server itself. > Du on the server shows the same as on the client - only a small amount used (36Gb used) whereas a df shows 152Gb used. I am using solaris and linux clients mostly. This happened on FreeBSD 4.6, and continues on this 4.9-RELEASE machine (same partitions, just an upgraded OS). Eric -- ------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Today is the tomorrow you worried about yesterday. ------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40A834B0.60806>