https://forums.qrecall.com/posts/list/5.page JForum - http://www.jforum.net https://forums.qrecall.com/posts/preList/144/614.page https://forums.qrecall.com/posts/preList/144/614.page GMT
If that's the case, it should work. QRecall is designed to capture from HFS+ volumes, but it can write an archive to just about any filesystem (MSDOS, Samba, UFS, ...). The archive itself is just a package (directory) that contains a set of flat files. The principle prerequisite is that the filesystem that contains the archive be able to efficiently, and correctly, handle large (multi-Gigabyte) data files.

So everything captured from your OS X volume (file data, metadata, ACLs, and so on) ultimately just become data in a flat file in the archive package.


]]> https://forums.qrecall.com/posts/preList/144/617.page https://forums.qrecall.com/posts/preList/144/617.page GMT https://forums.qrecall.com/posts/preList/144/618.page https://forums.qrecall.com/posts/preList/144/618.page GMT https://forums.qrecall.com/posts/preList/144/619.page https://forums.qrecall.com/posts/preList/144/619.page GMT https://forums.qrecall.com/posts/preList/144/620.page https://forums.qrecall.com/posts/preList/144/620.page GMT
The problem is a curious one. During the process of duplicating files inside the archive, QRecall encounters error -54, which is a generic "permissions error."

The oddity is this: at the point where the error occurs, QRecall has already created an written a number of other files successfully, so to suddenly get a "permissions error" seems inconsistent. Then again, it might be a peculiarity of the FSCopyObjectSync function (which is the call that's failing).

Here are two things to try that might help us narrow the problem.

1) Try NOT pre-authorizing QRecall to run with administrative privileges. It's possible that Samba or FSCopyObjectSync is becoming confused when the processes switches UIDs.

2) Try the release version of QRecall (version 1.0.1). Version 1.0 doesn't use the FSCopyObjectSync function. To install the release version (or any earlier version), first uninstall the current version by holding down the Shift+Option keys and choosing QRecall > Quit and Uninstall. Replace it with the older version and start it up again.]]> https://forums.qrecall.com/posts/preList/144/621.page https://forums.qrecall.com/posts/preList/144/621.page GMT https://forums.qrecall.com/posts/preList/144/622.page https://forums.qrecall.com/posts/preList/144/622.page GMT
However, there are potentially a number of solutions. Let me first investigate why FSCopyObjectSync is a problem on Samba shares and then look for a workaround.
]]> https://forums.qrecall.com/posts/preList/144/623.page https://forums.qrecall.com/posts/preList/144/623.page GMT https://forums.qrecall.com/posts/preList/144/624.page https://forums.qrecall.com/posts/preList/144/624.page GMT
]]> https://forums.qrecall.com/posts/preList/144/625.page https://forums.qrecall.com/posts/preList/144/625.page GMT
[quote]I've killed the process multiple times but it keeps respawning.[/quote]QRecallMonitor is installed as a launchd user agent. If you kill it, launchd just starts it again.

[quote]Is there a way to shut it down?[/quote]Not really, except by uninstalling QRecall or logging out.

[quote]I'm not sure if it's tied to the scheduler, but I don't have a desire to monitor du changes or schedule an automatic backup, etc.[/quote]It isn't tied to the scheduler, per se. It displays the status of the scheduler, scheduled actions, and the progress of independent actions started by the application. It also performs a number of useful tasks while you are logged in. Among other things, it monitors disk mount/unmount events and maintains the capture history information used by the QRecall contextual pop-up menu.]]> https://forums.qrecall.com/posts/preList/144/626.page https://forums.qrecall.com/posts/preList/144/626.page GMT
Thanks James. Looking forward to see if you're able to fix the silliness on my side. Would love to be able to use QRecall as it's the easiest and best solution I've found :)]]> https://forums.qrecall.com/posts/preList/144/627.page https://forums.qrecall.com/posts/preList/144/627.page GMT
One of the Apple network engineers thinks that the problem might be protocol interop issue. Would it be possible to capture a packet trace between the two machines during a capture? (I would suggest preforming a very small capture on a new archive, or else the trace will be huge.)]]> https://forums.qrecall.com/posts/preList/144/630.page https://forums.qrecall.com/posts/preList/144/630.page GMT
Some archive files are opened by several threads simultaniously. When a file is open by multiple processes, the access modes all have to be in harmony. When the access modes are translated into HFS or AFP access modes, QRecall is happy. But when the access modes are translated into SMB access modes, they apparently collide.

QRecall version 1.1.0(27) opens its index files using more restrictive access modes. Hopefully, these will translate into equally compatible SMB access modes.

If you want to try this again, download 1.1.0(27) and give it a try.
]]> https://forums.qrecall.com/posts/preList/144/658.page https://forums.qrecall.com/posts/preList/144/658.page GMT https://forums.qrecall.com/posts/preList/144/659.page https://forums.qrecall.com/posts/preList/144/659.page GMT https://forums.qrecall.com/posts/preList/144/680.page https://forums.qrecall.com/posts/preList/144/680.page GMT https://forums.qrecall.com/posts/preList/144/681.page https://forums.qrecall.com/posts/preList/144/681.page GMT https://forums.qrecall.com/posts/preList/144/682.page https://forums.qrecall.com/posts/preList/144/682.page GMT
I just looked at the log file you sent and it's a bit of a mystery. The capture is fails to write to the archive with OS error -51. This is an "invalid reference number" error.

When an application opens a file, it gets a "reference number" which it then uses to read and write to that file. When the file is closed, that reference number becomes invalid.

I can't think of any good reason why this might be happening. Some file/operating systems have limits about how many files can be open at once. I'm wondering if the SMB drivers on the PowerMac is losing track of what files it has open? Or maybe the volume is getting disconnected and reconnected (this happens all the time on my WiFi), and after reconnecting it has forgotten what files it had open? (I'm mostly thinking out loud here.) I'll post this question on one of the technical forums and see if anyone has any good ideas.]]> https://forums.qrecall.com/posts/preList/144/683.page https://forums.qrecall.com/posts/preList/144/683.page GMT https://forums.qrecall.com/posts/preList/144/688.page https://forums.qrecall.com/posts/preList/144/688.page GMT
Ralph]]> https://forums.qrecall.com/posts/preList/144/690.page https://forums.qrecall.com/posts/preList/144/690.page GMT https://forums.qrecall.com/posts/preList/144/692.page https://forums.qrecall.com/posts/preList/144/692.page GMT
I'm going to see if I have a spare external drive I can connect to the laptop and see if that works.]]> https://forums.qrecall.com/posts/preList/144/693.page https://forums.qrecall.com/posts/preList/144/693.page GMT https://forums.qrecall.com/posts/preList/144/701.page https://forums.qrecall.com/posts/preList/144/701.page GMT
I can find nothing in the code to explain what's happening. So for now I'm going with the assumption that the problem is coincident with using this particular storage device.

The first diagnostic is to try it with a different device. You were going to perform the same capture on the same machine using an external drive. Have you had a chance to do that, and were the results different?
]]> https://forums.qrecall.com/posts/preList/144/702.page https://forums.qrecall.com/posts/preList/144/702.page GMT https://forums.qrecall.com/posts/preList/144/703.page https://forums.qrecall.com/posts/preList/144/703.page GMT
I also wouldn't be surprised at all if there were subtle platform-specific differences between the Samba drivers on the G4 vs. those your Intel system.]]> https://forums.qrecall.com/posts/preList/144/704.page https://forums.qrecall.com/posts/preList/144/704.page GMT