On Thu, 2003-09-25 at 12:59, [EMAIL PROTECTED] wrote: > the logs came from /raid/ssl/..... so it's definitely on 'sda1' right? > 4.1G still taken up! weird... > does 'rm' completely remove it? I should think so... it just makes the > i-node free so it's as good as gone right? :(
Could be one of two things I can think of. - The file system usually reserves space for the root user, that's unavailable to regular users. You can check the reserved block count using dumpe2fs, and change it with tune2fs. If root is writing those files, then it will continue to write to them after df is reporting 100% usage, and removing them may not get you back below 100%. I think you'll find, if you run df without the -h option, different figures for the total size and used space on the full partition, indicating this is the cause. - Some process or other may be holding the deleted files open still. If a file is open when it is deleted, then its directory entries are deleted, but the file is still hanging around, and the space won't be freed until the program using that file closes it. access_log is an apache log file, right? If so, try stopping and starting apache and seeing if that clears it up. -- Pete -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
