> I did find a file in /var/log that was partly to blame, I also removed some > un-needed packages. However I'm still trying to figure out where this space > went. Tim mentioned the mount issue which might be a clue, I had a > mountpoint of /backups pointing to an external USB device which was having > issues (turned out to be an issue with the filesystem, I changed from reiser > to ext3 and the problem went away) ... so the question I have, my > understanding is that if /backups was having issues the parent partition > which is / which is a completely different device, it is possible that junk > was getting written to / because of the issue with /backups ? If that is > indeed the case, I'm wondering where I can find that garbage data which is > sucking up space. I have gone through each of the dir's mounted under / and > they don't add up to the amount showing up in df ... I have all my configs > and required packages that I built from source available to me so starting > over wouldn't take very long. I'm just wondering if there is a way to figure > this out before going to that extreme. > > Would the fact that the partition was created with 1k blocks instead of 4k > blocks?
if /backups wasn't really mounted for a while and data was written to /backups (on /), then you remounted /backups you would see this issue. umount /backups and then see if there is data in /backups (on /). also, rather than adding things together you can use the -x switch to du to tell it not to cross mountpoints. so du -sx / will show the space used on / without crossing into /home, /backups, etc. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
