Good idea Neil. The problem is tho that the space comes back as soon as he reboot. That makes it "unlikely" it would be the log files. Why would they decrease just because he rebooted? I Would have thought virtual memory is much more likely, that is the area I would have searched in the pc world. And I don 't claim to be any expert so I'm always looking to learn. But you are right, the first thing to do is identify what file is growing and then work from there. I must admit from many years in many operating systems that I don't like installing major upgrades over older operating systems (10.5 over 10.4). But that is what we have to work with so lets deal with it. Find the file (files) that keep getting bigger and then we can go from there. cjc On 26/01/2008, at 10:17 AM, Neil Laubenthal wrote: > On Jan 25, 2008, at 11:42, Robert wrote: > >> So far nothing has worked. I have tried everything that everyone >> has suggested. If I reboot I will have 40 gb and I can watch it >> drop. Last resort will be to back up and reformat and do a clean >> install. Not looking forward to doing that but it will be a last >> resort. It would be nice to figure out what is causing this. As I >> had 10.4 on this drive before installing 10.5 I wonder if there is >> something that I had on the drive that 10.5 does not like. Anyway >> thanks for all of the suggestions. Bob > > to figure out. > > My guess is still console logs, if the space continues to go down > until the drive is full then this seems the only likely candidate to > me . . .it's certainly not VM. Have you checked to make sure that > they aren't the problem (launch console and the left pane will show > you the locations of the various log files . . . navigate separately > in Finder to those locations and look for huge files. It's likely > _not_ a whole buttload of small files; it's much more likely to be a > single really large file that is eating up the space. > > neil