Shirt Pocket Discussions

Shirt Pocket Discussions (
-   General (
-   -   How fast... (

macbenutzer 03-17-2006 05:42 PM

How fast...
Hi all,

i am having trouble with SuperDuper:
- it crashed my computer a few times now.
- it runs MUCH slower than i remember.

It copies (Smart BackUp) my Sytem-HD to an attached FireWire800-HD with an effective copy speed of 6-7 MB/s. The destination drive is clean and empty. As i remember was SuperDuper copying files much faster "before". I can not say that i changed anything in SD - i did update my System from 10.4.4 to 10.4.5. I DID repair permission before and the system is running very stable - except SD...

How fast should SD copy "normally" (120GB with big and small files -> 467.000 files in all) ?

System: OS X 10.4.5 / G5 2x2 orig / 4,5 GB RAM

dnanian 03-17-2006 05:46 PM

If you're doing a full erase-then-copy on a Power PC based system, you're going to see copy speeds of 6-8MB/s or so. Subsequent Smart Updates will be significantly faster, which is likely what you remember.

On an Intel-based Mac, you'll see 10-16MB/s or so, because their I/O subsystems are faster.

As far as "crashing your computer" is concerned, it's very hard for a user-level process like SuperDuper! to crash your computer itself. Instead, kernel-level processes (like FireWire or disk drivers, etc) do so. More details would help me help you figure out what's wrong there.

macbenutzer 03-17-2006 07:57 PM

More details...
Ok - i just had a look into the logs and hope this one helps a bit... i can not read it:

- - -

Fri Mar 17 22:17:35 2006
panic(cpu 0 caller 0x0003FEA8): zalloc: "kalloc.64" (11996544 elements) retry fail 3
Latest stack backtrace for cpu 0:
0x00095718 0x00095C30 0x0002683C 0x0003FEA8 0x0002BB0C 0x0007BF9C 0x0007C1C4 0x0028984C
0x000DD738 0x000DCBEC 0x00228F54 0x000FC160 0x000F5738 0x0027D92C 0x0027D668 0x002AA2E4
0x000ABEB0 0x6C743B64
Proceeding back via exception chain:
Exception state (sv=0x5D855C80)
PC=0x9001450C; MSR=0x0000D030; DAR=0x35493000; DSISR=0x42000000; LR=0x00004B50; R1=0xBFFFF900; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.5.0: Sun Jan 22 10:38:46 PST 2006; root:xnu-792.6.61.obj~1/RELEASE_PPC

- - -

SD had copied something about 1/3 of the 120GB and crashed the system completly (well - maybe not SD itself but while copying with SD it crashed - without running SD the computer runs ok).

I will retry it once more tomorrow morning (i do not want to leave the computer without looking on it from time to time).
Maybe if you have another hint where to look for that error...?

Best regards - Peter

By the way: can i change my "Name" on this list?
"@mac" was added by Safari - i did not notice it before hitting return.

dnanian 03-17-2006 08:04 PM

That looks like bad memory, Peter...

I'll update your name to remove the @mac...

macbenutzer 03-18-2006 03:06 PM


thanx for chaning my name :-)

It was/is a HD-Error:
I had a RAID 1 installed (2x 160GB) and one disk crashed and left the other one with an error in the directory.
I managed to backup the system manually (i hope) and will get it for further checking to my Mac-dealer on monday (he is faster and knows better than me).

There is a corrupt folder with 4.5 GB mp2-data - all Paris-Dakar-2006 :-(
I could not delete them. SuperDuper crashed when trying to copy them. So did HD-Utility...

Are you sure about the bad memory ? I will have to forward this to my dealer then.


dnanian 03-18-2006 03:16 PM

No, there's no way for me to be sure. It's just in a kernel allocator, and it was an educated desk. If you've got some seriously corrupt folders, it's quite possible that those errors are causing the kernel to do something wrong in memory allocation... but since you didn't mention the fact that things were corrupt there was no way for me to guess that. (All you said was that, since the update, SD! is crashing your system -- but it doesn't seem isolated to SD! any more...)

All times are GMT -4. The time now is 08:43 PM.

Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2022, vBulletin Solutions, Inc.