Capture issues

I backup two computers to the same archive, backing up user files every day and backing up the full drives weekly to pick up system changes, etc. This system runs smoothly so I don't pay much attention to it most of the time. I've just noticed that for the past couple of months the log has been showing "Capture issues" for the full disk backups from both computers. The user files backups on both commuters seem to be fine. I just noticed the problem after installing the latest beta, but it was apparently going on for a while before that.

On my MacBook Pro the problem seems to be the same every time, as follows:

Action 2012-01-21 08:17:26 Capture mbhd
Action 2012-01-21 08:17:41 Minutia Locating changes since Saturday, January 14, 2012 12:24 PM
Action 2012-01-21 08:29:25 Capture issues
Action 2012-01-21 08:39:04 volume mbhd
Action 2012-01-21 08:29:25 folder dev
Action 2012-01-21 08:29:25 Curious Could not determine display name
Action 2012-01-21 08:29:25 cannot get display name
Action 2012-01-21 08:29:25 Error: Unexpected internal error
Action 2012-01-21 08:29:25 Minutia Path: /dev
Action 2012-01-21 08:29:25 Minutia OSErrName: kLSUnknownErr
Action 2012-01-21 08:29:25 Minutia OSErr: -10810
Action 2012-01-21 08:39:08 Captured 394 items, 1.62 GB (56% duplicate)
Action 2012-01-21 08:39:29 ------- Capture finished (22:05)

On he iMac, the problem sometimes identifies as "folder dev" with nothing deeper showing, like this,

ction 2012-01-15 01:00:00 ------- Capture to 2nd backup.quanta
Action 2012-01-15 01:00:00 archive: /Volumes/FantomHD/2nd backup.quanta
Action 2012-01-15 01:00:05 Capture iMacHD
Action 2012-01-15 01:00:22 Capture issues
Action 2012-01-15 01:06:48 volume iMacHD
Action 2012-01-15 01:00:22 folder dev
Action 2012-01-15 01:06:50 Captured 146 items, 4.35 GB (94% duplicate)
Action 2012-01-15 01:06:54 ------- Capture finished (06:49)

and sometimes show a deeper tree of issues down into Circus Ponies Notebook

Action 2012-01-22 01:00:01 ------- Capture to 2nd backup.quanta
Action 2012-01-22 01:00:01 archive: /Volumes/FantomHD/2nd backup.quanta
Action 2012-01-22 01:00:15 Capture iMacHD
Action 2012-01-22 01:00:48 Capture issues
Action 2012-01-22 01:17:46 volume iMacHD
Action 2012-01-22 01:17:46 Applications/Apps-misc/CircusPoniesNoteBook2.1
Action 2012-01-22 01:00:48 folder NoteBook.app
Action 2012-01-22 01:01:03 NoteBook.app
Action 2012-01-22 01:00:49 folder Contents
Action 2012-01-22 01:01:03 Contents
Action 2012-01-22 01:00:49 folder Frameworks
Action 2012-01-22 01:01:03 Frameworks
Action 2012-01-22 01:00:51 folder MacOS
Action 2012-01-22 01:00:51 folder Resources
Action 2012-01-22 01:01:03 Resources
Action 2012-01-22 01:05:23 folder dev
Action 2012-01-22 01:17:48 Captured 440 items, 4.84 GB (93% duplicate)
Action 2012-01-22 01:17:58 ------- Capture finished (17:42)

How much should I worry about this? Is it just telling me that a few particular files didn't get captured, or is there some more problematical going on here?

Ralph

There's a problem/bug in Lion wherein an attempt to access the /dev directory on the startup volume using the core filesystem APIs results in an I/O error.

It doesn't happen on all systems, and it doesn't happen all the time. For months I was unable to reproduce this problem, and then last week my primary development system started showing the same symptoms. I've filed a bug report with Apple a few days ago. It's such a bizarre and blatant error that I'd be surprised if they're not already aware of the problem, but I don't know what's being done about it.

I'm 80% sure that this is an innocuous problem, but I need to do more testing to be sure. Normally, there's nothing in the /dev directory for QRecall to capture, since it's populated almost exclusively with logical device files. So not capturing it shouldn't make any difference.