https://forums.qrecall.com/posts/list/3.page JForum - http://www.jforum.net
Couldn't open the archive afterward; had to repair it first. Verified the volume first and ran into incorrect file hard links numbers (or something like that) error. The disk was repaired successfully and then so was the archive.

Tried to compact again, and ran into the same error again, only this time disk verification turned up no error and the archive was successfully repaired.

Tried to compact other archive and haven't run into similar trouble so far. Could be something wrong with the disk, or the archive.]]> https://forums.qrecall.com/posts/preList/524/2425.page https://forums.qrecall.com/posts/preList/524/2425.page GMT
I made a backup copy of the archive before going v2, which can be compacted without issue.]]> https://forums.qrecall.com/posts/preList/524/2426.page https://forums.qrecall.com/posts/preList/524/2426.page GMT https://forums.qrecall.com/posts/preList/524/2428.page https://forums.qrecall.com/posts/preList/524/2428.page GMT
Note in the screenshot that the two ghost items were scheduled for 0:00, but the system time was at 0:28 already. Clicking any of the item on the second pop-up (Stop, Stop and Reschedule, etc.) does nothing. Guess I'll have to reboot to get rid of them.]]> https://forums.qrecall.com/posts/preList/524/2430.page https://forums.qrecall.com/posts/preList/524/2430.page GMT Got it, and thanks for the test archive. I don't think I would have found the bug without it.

Yes, this is why we do beta testing. :-)

This archive had just the right (wrong?) sequence of reads and writes needed to confuse the redundancy buffer management. The fix for this will be in b11.]]> https://forums.qrecall.com/posts/preList/524/2436.page https://forums.qrecall.com/posts/preList/524/2436.page GMT This is an unrelated bug that I'm working on.

Workaround: Quit the QRecall Monitor process to make them go away.]]> https://forums.qrecall.com/posts/preList/524/2437.page https://forums.qrecall.com/posts/preList/524/2437.page GMT