Thanks James, I have followed your suggestion with disk utility and it does not report any problems. I'll continue to keep an eye on it.

Out of curiosity, does QRecall even backup anything from /dev? as I was under the impression it more of a "virtual directory" and those are not even "real" files, but special device files.

Thanks for the continued improvements in the software, I'm very happy with it and it meets my needs far better than the alternatives I've tried.

victor

I'm suddenly getting this "unexpected event" (labelled with a question mark in the log window), which I believe coincides with me installing the latest Beta (54) as I never saw it before that.

Since it is marked as a "curious" error, I'm not overly concerned about it, but I just wanted to mention it. I have pre-authorized again, just in case it was connected to that, although that didn't fix it.

folder dev / Could not determine display name / cannot get display name for Path: /dev

2011-12-09 23:02:11.495 -0500 #debug# 0x00007fff873d38bf: 0x00007fff873d3770 _pthread_start (/usr/lib/system/libsystem_c.dylib@0x00007fff87385000) [2.734480.9144.73.1.7.17]
2011-12-09 23:02:11.495 -0500 #debug# 0x00007fff873d6b75: 0x00007fff873d6b68 thread_start (/usr/lib/system/libsystem_c.dylib@0x00007fff87385000) [2.734480.9144.73.1.7.18]
2011-12-09 23:02:11.495 -0500 #debug# -[CaptureProcessor beginProcess] user unreachable directory: ANTARES:dev [2.734480.9144.74]
2011-12-09 23:02:11.495 -0500 #debug# +[MetadataPorter getIconRefFromFile:filename:catInfo:infoBitmap:visible:] [2.734480.9144.75]
2011-12-09 23:02:11.495 -0500 #debug# Metadata request failed [2.734480.9144.75.1]
2011-12-09 23:02:11.496 -0500 #debug# IO exception [2.734480.9144.75.1.1]
2011-12-09 23:02:11.496 -0500 Details Error: I/O error (bummers) [2.734480.9144.75.1.2]
2011-12-09 23:02:11.496 -0500 Minutia OSErrName: ioErr [2.734480.9144.75.1.3]
2011-12-09 23:02:11.496 -0500 #debug# API: FSPathMakeRefWithOptions [2.734480.9144.75.1.4]
2011-12-09 23:02:11.496 -0500 Minutia OSErr: -36 [2.734480.9144.75.1.5]
2011-12-09 23:02:11.496 -0500 Minutia Path: /dev [2.734480.9144.75.1.6]
2011-12-09 23:02:11.496 -0500 #debug# backtrace [2.734480.9144.75.1.7]

I occasionally get errors like the following related to extended attributes:

2011-06-14 00:37:10.471 -0400 Caution Unable to read extended attribute data [2.734301.17269.70]
2011-06-14 00:37:10.518 -0400 Details path: /Volumes/audiolib/music/lossy/Don_Williams [2.734301.17269.70.1]
2011-06-14 00:37:10.519 -0400 Details xattr: com.apple.metadata:_kTimeMachineNewestSnapshot [2.734301.17269.70.2]
2011-06-14 00:37:10.519 -0400 Details errno: 22 [2.734301.17269.70.3]
2011-06-14 00:37:10.880 -0400 Caution Unable to read extended attribute data [2.734301.17269.71]
2011-06-14 00:37:10.880 -0400 Details path: /Volumes/audiolib/music/lossy/Don_Williams [2.734301.17269.71.1]
2011-06-14 00:37:10.880 -0400 Details xattr: com.apple.metadata:_kTimeMachineOldestSnapshot [2.734301.17269.71.2]
2011-06-14 00:37:10.880 -0400 Details errno: 22 [2.734301.17269.71.3]

In this case it appears to be a timemachine attribute, but I've seen other attributes cause this message ("quarantine"). I'm not currently using time machine, but have done so in the past (before I started using QRecall).

My main concern is that the file itself is being backed up properly when I see this error (I don't care so much about the extended attribute).

I'm using QRecall 1.2.0.35. I don't remember if I saw these warnings using the previous version (1.14). Curiously, I only see it on files in my music library which are stored on a NAS.

thanks,

victor

EDIT: Sorry, I just noticed that somebody else had posed the same question in the forum back in 2010