My iTunes library is on a mirrored pool which reports that it is healthy.
A scrub resulted in 0 errors and 0 repairs.
A SMART check reports both disks as healthy.
- Code: Select all
pool: Prometheus
state: ONLINE
scan: scrub repaired 0 in 3h58m with 0 errors on Thu May 2 14:23:22 2013
config:
NAME STATE READ WRITE CKSUM
Prometheus ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
GPTE_E53D30CB-21A9-4CDE-957E-6A430782F10D ONLINE 0 0 0 at disk3s2
GPTE_F3D67F38-4340-4936-B233-E7E92FDF89FA ONLINE 0 0 0 at disk4s2
errors: No known data errors
In console logs I am seeing an unresolved trace error for *many* tracks (945 instances before I force quit iTunes this time):
- Code: Select all
5/3/13 3:56:33.660 PM iTunes[3268]: Possible unresolved transaction race -104/(/path to library/filename)
I found this thread about laggy performance with mention of similar race errors where the problem was resolved by recreating the pool.
http://zevo.getgreenbytes.com/forum/viewtopic.php?f=7&t=1537&start=10#p3148
I'd really rather not recreate the pool. I do have backups on my NAS4Free zfs box, it's the time it will take to restore that gets me down...
I also found some evidence that these errors result when folks run their iTunes library over SMB or on non-HFS+ disks. The errors resolve then they switch to an AFP share.
https://discussions.apple.com/thread/2185982?start=0&tstart=0
iTunes has been working reasonably well until this week. There were occasional freezes, but I do have an old, large, disorganized library and iTunes is a bit of a donkey at times so I wasn't concerned. Perhaps it was this problem getting steadily worse all along?
Any suggestions are very welcome!
Thanks,
Geoff