QRecallDownloadIdentity KeysForumsSupport
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Groups] Back to home page 
encryption dilemma  XML
Forum Index » Problems and Bugs
Author Message
James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1473
Offline

Ralph Strauch wrote:I think I've that sorted out now, and am back to one key per computer. I assume I can just delete the extra layer that I created unintentionally without affecting the rest of the backup

A more surgical approach would be to find the "new" volume in the other owner and simply delete that from the archive. That way, you don't have to delete any subsequent layers.

I had set the Current Encryption Limit to 2 after you suggested 1 or 2, but I'll take it down to 1 now.

Let me know how that goes, or just send another diagnostic report when you get back.

I seldom even log onto the iMac, but it looks like Qrecall could run scheduled backups of the whole iMac from my account without my being logged in. Is that correct, and should that satisfy the router's desire for a single common user? (I'm uid 501 on both machines.)

Here's the important concept:

The account on your computer is independent of the account you use on the file server.

This is the concept that is most confusing when working with networked volumes. It does NOT matter what your user account is. The files written to your file server will belong to the (server) account you use to authenticate with when you connect to the server.

If you and your wife can get set up so that both of your local accounts connect to the file server using the same server account, then the files (archives) on the shared volume will belong to both of you, and it doesn't matter what your local account is or what UID you're using.

The reason I'm short on practical advice is that different file servers, NAS devices, and so on handle this differently. For example, Apple's Airport Time Capsule has (basically) two different authentication modes for its shared disk: shared and per-account. The "shared" modes allow all network users to access the files on the Time Capsule as if they were all the same user. This is the effect you need, and this is the mode I use with my Time Capsules. All QRecall users can connect to the Time Capsule and use the same archives, since (from the Time Capsule's perspective) they are all the same user. If I switched my Time Capsule to the per-account mode, I'd have the same problem you're experiencing.

Other devices handle accounts and ownership differently. Some server/NAS devices, for example, deliberately extend file ownership to the shared volume using your local account ID, effectively emulating an external drive. So YMMV and you'll need to find the magic combination that works for you.

- QRecall Development -
[Email]
Ralph Strauch



Joined: 24-Oct-07 22:17
Messages: 194
Offline

After three weeks away, I'm back again trying to get Qrecall to work with my new router. I'm now able to see, read, and write to disks mounted on the router. My regular archive still won't open, though, but still continues to hang with the "This archive is being updated ..." notice and never obtains the semaphore lock. I was able to create a small test archive, though, which closes and reopens normally. The problem seem to be just with the larger archive. I'm sending a Report.

Ralph
James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1473
Offline

Ralph,

Looking at the logs, QRecall is still stuck trying to obtain (and later break) the shared file semaphore. I suspect a permissions problem, but it's hard to tell from the logs.

I'd be very much interested in knowing the ownership and permissions of all of the files in both the archive that is stuck and the one that is working. If you have the time, open an Terminal window and issue this 'ls' command for each archive:

email the results, or post them here.

- QRecall Development -
[Email]
Ralph Strauch



Joined: 24-Oct-07 22:17
Messages: 194
Offline

Here are those listings, with some explanation.

The first listing is from a folder containing only the archive, 3rd which I had moved to a separate folder because it felt like the router would be easier to configure if the shared file was in a separate folder than if it was at the top level.

The second listing is from the volume containing my test archive, named testbackup.quanta. When I saw the hidden files that this directory contained I thought maybe that was the problem -- that when I moved 3rdbackup.quanta into a separate folder I had not move some invisible file that it needed in order to open. So I moved it back to the top level of that volume.

That didn't solve the problem. testbackup.quanta will open properly, but 3rdbackup.quanta hang with the "file in use" message.


First listing: 3rd backup.quanta in a separate folder/volume2/backup


2nd listing: directory containing testbackup.quanta at top level



third listing Directory containing 3rdbackup.quanta returned to top level in /volume2

This message was edited 1 time. Last update was at 16-Jan-17 09:48

James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1473
Offline

Ralph,

Thanks for the info, but it wasn't quite what I was looking for. I'm interested in seeing the insides of the archive packages. These commands should do the trick:

I'm interested in the ownership, permissions, and existence of the various .lock and .share semaphore files inside the archive package.

- QRecall Development -
[Email]
Ralph Strauch



Joined: 24-Oct-07 22:17
Messages: 194
Offline

Here they are



This message was edited 1 time. Last update was at 16-Jan-17 15:49

James Bucanek



Joined: 14-Feb-07 10:05
Messages: 1473
Offline

So the mystery is that you can open and capture files to testbackup.quanta, but you can't open and capture files to 3rd backup.quanta.

I don't see any differences in the ownership or permissions for the two archives, and I don't see any stale .lock or .share files that might be blocking access to it.

So, the only thing I can think of at this point is that the file server supports file locking and/or advisory locks and is holding an orphaned lock on one of the files in 3rd backup.quanta. This can happen when a network clients obtains a lock on a file and then gets disconnected from the server.

This can usually be solved by restarting the server. If this is a network device that runs 24/7, it's easy for orphaned locks to stay around for weeks. (Note that in cases like this, restarting the clients won't have any effect on the problem.)

If that doesn't work, you can try repairing the 3rd backup archive (presuming you have enough free space), choosing the "Copy recovered content to new archive" option (say 4th backup archive). QRecall will extract all of the data in the original archive and use it to create a brand new one. When finished, you can discard the old archive.

This message was edited 2 times. Last update was at 16-Jan-17 17:53


- QRecall Development -
[Email]
 
Forum Index » Problems and Bugs
Go to:   
Powered by JForum 2.1.8 © JForum Team