Kernel Panic when using rsync

[GoogleCodeExporter]

I was using rsync to copy my itunes library to a raids, newly created. 
Apparently the first  time was using cp -rp to copy it died somewhere at about 
140GB of 180GB. Twice I tried restarting by using rsync and each time it kernel 
paniced almost immediately.

This is 10.9, QUO-based Hackintosh, 16G DDR3 1600 RAM, Intel i7-3770k not over 
clocked.  Copy from (damn slow) Drobo.

scrub found no errors.

I am running disk utilities to check the Drobo.

Original issue reported on code.google.com by alanruttenberg@gmail.com on 24 Nov 2013 at 12:58

• Merged into: #120

Attachments:

• Kernel_2013-11-23-180009_Den.panic
• Kernel_2013-11-23-193125_Den.panic

[GoogleCodeExporter]

Installed MacZFS-74.3.2.pkg and problem persists. A copy of 625M succeeded but 
immediately after the rsync attempt did it again

Original comment by alanruttenberg@gmail.com on 27 Nov 2013 at 6:47

[GoogleCodeExporter]

Thanks for the report.  I had a first look at your panic files: Both describe 
the same call path, and both crashes happen *outside* the MacZFS code.  While 
this does not exclude that it is MacZFS' fault, it means that some other part 
of the kernel crashes.  Finding out if and how this relates to specific actions 
(not) taken by MacZFS will be very difficult.

Can you provide additional details on your system setup and what was happening 
while or shortly before the crash happened?

Especially:
- Disks and how they are connected
- ZFS pool layout (zpool list; zpool status -v; zpool get all; zfs list)
- ZFS memory usage: search the kernel log for lines containing "zfs" or "ZFS"
- "zfs get all file_system_name" for the ZFS file system "file_system_name" 
involved in the transfer that crashed.
- Are you copying to or from ZFS at the time of the crash?  (I assume "to")
- What is a "Drobo"? (Never heard that term or name)
- are you using Apple's rsync or a custom build (e.g. MacPort, Homebrew, ...)?  
what is the output of "rsync --version"?
- Does rsync seem to crash always at the same folder / files, or after a random 
time (as fas as this can be judged from the three samples you have)?
- Where other CPU or Disk intense programs running at the time of the crash?
- Was the system trying to go to sleep?

Thanks & sorry for the troubles

Original comment by googlelogin@bjoern-kahl.de on 27 Nov 2013 at 9:10

[GoogleCodeExporter]

This is a duplicate of issue 120, fixed with commit 58854f77.
Release target: 74.3.3 (February / March)

Original comment by googlelogin@bjoern-kahl.de on 15 Feb 2014 at 12:15

• Changed state: Duplicate