[utentemedio]

When I try to delete (actually when I empty the trash) some files (generally large files, i.e. some hundreds of MB) that has been downloaded using XNap (a JAVA based p2p sofwware) a system crash occur!

I attached the log file below (unfortunately I am not so expert to understand it).
This problem occur on the internal HD of my PowerMac G5 Dual 2GHz, with OS X 10.3.9.

I also tried to delete these files using this mac in Firewire Target mode from a PowerBook G4 with OS X 10.4.3, but when I try to empty the trash the same kernel panic occur on the PowerBook.

Has somebody any explanation of that?

Please help me to remove these files without (if possible) reformatting the HD.

Thanks to all of you

Francesco



panic(cpu 0 caller 0x00102164): jnl: transaction too big (3142144 >= 3145216 bytes, bufsize 4096, tr 0x2623fb0 bp 0x326ccc90)

Latest stack backtrace for cpu 0:
Backtrace:
0x00095698 0x00095BB0 0x0002683C 0x00102164 0x0021AF3C 0x00242B18 0x0023FD7C 0x00245014
0x0024533C 0x002453D4 0x00246150 0x0022AE54 0x0022B068 0x00239558 0x002390DC 0x000FC4BC
0x000EE14C 0x002A9BF4 0x000ABE30 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x384FFA00)
PC=0x9000606C; MSR=0x0200F030; DAR=0x00304010; DSISR=0x42000000; LR=0x90B279E8; R1=0xBFFFC0F0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.3.0: Mon Oct 3 20:04:04 PDT 2005; root:xnu-792.6.22.obj~2/RELEASE_PPCModel: PowerBook5,3, BootROM 4.7.1f1, 1 processors, PowerPC G4 (1.1), 1.33 GHz, 1.5 GB
Graphics: ATI Mobility Radeon 9600, ATY,RV350M10, AGP, 64 MB
Memory Module: SODIMM0/J20STANDARD, 1 GB, DDR SDRAM, PC2700U-25330
Memory Module: SODIMM1/J23REVERSED, 512 MB, DDR SDRAM, PC2700U-25330
AirPort: AirPort Extreme, 404.2 (3.90.34.0.p16)
Modem: LastDash, Euro, V.92, 4.0, APPLE VERSION 2.6.6
Bluetooth: Version 1.6.6f22, 2 service, 0 devices, 1 incoming serial ports
Network Service: Built-in Ethernet, Ethernet, en0
PCI Card: TXN,PCIXXXX-00, cardbus, PC Card
Parallel ATA Device: MATSHITADVD-R UJ-816,
Parallel ATA Device: HTS541010G9AT00, 93.16 GB
USB Device: Bluetooth HCI, , Up to 12 Mb/sec, 500 mA
FireWire Device: LaCie d2 Extreme LUN 0, LaCie Group SA, Up to 400 Mb/sec
FireWire Device: Target Disk Mode, AAPL, Up to 400 Mb/sec

[Detrius]

You likely have a corrupt directory structure. You can try repairing it with Disk Utility. If that fails, run Disk Warrior (or start with Disk Warrior if you already have it). Theoretically, it could be a hardware problem as well, but the odds of hardware causing this specific an issue are virtually nil. Also, with a directory structure messed up enough to cause a kernel panic, Disk Warrior may not be able to repair the damage, but it's definitely worth a shot.

[brokenjago]

Tell us how that goes.

[utentemedio]

Dear Detrius,
thank you very much for your help. I will follow your suggestion as soon as I find (I have already ordered it and it should arrive in dwe days) another hard disk to do a full back-up and to install another OS from which I can run Disc Utility and Disk Warrior on my internal HD.
I will let you know how it goes.
Best wishes
Francesco

[SMacTech]

I had this same problem. Whenever I accessed a certain file, Kernel Panic. Copy everything off and low-level reformat was the only solution. I suspect a bad block that subsequently was locked out after the reformat.

[Detrius]

Originally Posted by SMacTech

I had this same problem. Whenever I accessed a certain file, Kernel Panic. Copy everything off and low-level reformat was the only solution. I suspect a bad block that subsequently was locked out after the reformat.

Technically, low-level format is only something that can be done with SCSI drives. You can zero all data on an ATA drive, which maps out bad blocks. However, if a zero-all-data must be done to make the drive work, then you really have to replace the drive. Any bad blocks means the drive is unreliable. The only thing I would store on a drive that's had bad blocks is a porn collection.

[SMacTech]

Originally Posted by Detrius

Technically, low-level format is only something that can be done with SCSI drives. You can zero all data on an ATA drive, which maps out bad blocks. However, if a zero-all-data must be done to make the drive work, then you really have to replace the drive. Any bad blocks means the drive is unreliable. The only thing I would store on a drive that's had bad blocks is a porn collection.

You are correct though, it was not low-level formatted, my grey-beard showing, sorry. I re-initialized the drive by writing to every sector of the drive. The previous sector, which the OS was unable to access without a KP ensuing was no longer an issue and has been working reliably ever since.