Deleting .log file crashes system, please help.

[narco]

So I noticed that I have a .log file for SSX (a soulseek client) that is over 20GB large. I send the file to the trash, then I go to empty the trash and I get a Kernel Panic. I even tried deleting the file on a backup hard drive and it did the same thing.

Now, I don't know much about this kind of stuff, so how do I delete this file? I was going to try renaming the file to a ifjiodjiofjdoi.fij or something and then deleting it to see if that works, but that's probably dumb so I thought I'd ask first.

Thanks,
narco.

 

[narco]

How to delete a 20GB file?

OK, after some work, I tried a few things. I know that I can delete the .log file, but it still gives me kernel panics. i tried a number of utilities (like Force Delete 1.2 and Obliter8) which are supposed to delete "pesky" files that the trash won't delete. Still freezes up.

I also tried starting up from the Tiger DVD and deleting the file from there, but I guess I'm old school and you can't boot from a disc any longer. Can anyone help?

 

[Mitthrawnuruodo]

Have you tried Terminal?

sudo rm /path/to/logfile.log

Make sure you have NO spaces in the /path/to/logfile.log!!!

Or use something like MainMenu to "Clean All Logs".

 

[narco]

so if i moved the file to the desktop, i would write in the terminal:

sudo rm /computer/harddrive/Users/Name/Desktop/Console.log

?

Thanks!

 

[Mitthrawnuruodo]

Yes.

So you can move it... just not to trash?

Edit: Wait a minute? Is this one of the console.log (note the small 'c') files in /Library/Logs/console/501/? If so: I would probably try the MainMenu way first...

 

[narco]

yep, tried it and the same thing happened.

yeah, i can move it, rename it, anything -- it's just the second i empty the trash, the kernel panic occurs.

This is the error i get from the panic.log:

Sun Dec 17 08:28:13 2006
panic(cpu 1 caller 0x001023CC): jnl: transaction too big (8385024 >= 8388096 bytes, bufsize 4096, tr 0x40e6f7c bp 0x52171660)

Latest stack backtrace for cpu 1:
Backtrace:
0x00095138 0x00095650 0x00026898 0x001023CC 0x0021C0EC 0x0024188C 0x0024417C 0x00241294
0x0024652C 0x00246854 0x002468EC 0x00247668 0x0022C068 0x0022C284 0x0023A9B0 0x0023A534
0x000FC4A0 0x000EDF70 0x002AAE28 0x000AB930 0x4D447269
Proceeding back via exception chain:
Exception state (sv=0x5A14A000)
PC=0x9001AECC; MSR=0x0200D030; DAR=0xA0000574; DSISR=0x0A000000; LR=0x00003168; R1=0xBFFFFAA0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC

 

[narco]

OK, I repaired my disk and everything is cool now.

Unfortunately, when I went to delete the file, it went missing. I searched for it in spotlight and I even used a program to show hidden files, but nothing.

So it's there somewhere because I still only have 3.8GB of space left, but it's nowhere to be found. Oh well, at least everything is running properly!

 

[bousozoku]

It's probably a good idea to leave the System.log and Console.log alone.

You can probably delete any other log file by moving it to the Trash, restarting, and then, emptying the Trash. This should ensure that it's not in use.

 

[mac-convert]

If you look in your Applications | Utilities folder, you will find something called "Console". If you open that, it presents your "log files" to you in a viewer. By default it displays the console.log - with an option to clear it, and I would have to assume safely. You also have the option to open, examine and clear the system log - look under the File menu item. In the Open Quickly selection, you have access to many of the other logs kept within the system. This utility takes care of clearing and creating a new empty log file so the system can continue on about it's business. Here's hoping that you can get back to the point where you can clear the logs successfully.