You shouldn't rebooted it. There are times that a deleted/moved/archived etc are still being used by a user/process and the file/s are still open leaving the inode exist in fs.
The best practice for this is to make sure that the files you are moving/deleting/archiving is not being used. To check, run lsof on the partition, if there are still open files, kill it and perform housekeeping. Hope this help. Jimmy On Wed, Feb 16, 2011 at 10:31 AM, Bopolissimus Platypus Jr < bopolissimus.li...@gmail.com> wrote: > On Wed, Feb 16, 2011 at 1:38 PM, Bopolissimus Platypus Jr > <bopolissimus.li...@gmail.com> wrote: > > so there's close to 20GB unaccounted for. Has anyone experience with > > something like this? any hints? > > Never mind, solved. I just rebooted. Likely some process had created > some huge file, the files had been removed and then something that > still had open handles to those files didn't exit. Rebooting killed > all processes, so the inodes could be freed > and df and du now agree. > > I still don't know what was doing that, but I'm ok with that for now. > > tiger > > -- > Gerald Timothy Quimpo http://bopolissimus.blogspot.com > bopolissimus.li...@gmail.com bopolissi...@gmail.com > > Even Tom Lane said: "Or, if you're worried > about actions from functions, use a trigger > to do the logging. There are approximately > no cases where a rule is really better than > a trigger :-( " > _________________________________________________ > Philippine Linux Users' Group (PLUG) Mailing List > http://lists.linux.org.ph/mailman/listinfo/plug > Searchable Archives: http://archives.free.net.ph >
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
