Ticket #60 (closed defect: fixed)

Opened 1 year ago

Last modified 1 year ago

Fatal Error: Error opening file /home/mocha/.pybackpack/sets/filelist

Reported by: mochaRHW Assigned to: Andy
Priority: high Milestone: Stable
Component: backend Version:
Severity: major Keywords:
Cc:

Description

Umm, am I missing something here?

I setup a very simple backup using the "New Backup Set..". When I execute the backup, your program seems to be looking for the filelist file in the wrong place!

In this particular case the "filelist" is actually in: /home/mocha/.pybackpack/sets/testbackup/filelist

where "testbackup" was the name of the Backup Set.

I've tried this numerous times and the program always fails to look in the proper directory for the "filelist". WTF am I doing wrong??

Using pybackpack v0.5.3, rdiff-backup v1.1.14, under Ubuntu Fiesty with Gnome 2.18 and 2.6.20-16-generic kernel.

Change History

23/12/07 02:07:50 changed by Andy

  • priority changed from normal to high.
  • status changed from new to assigned.
  • severity changed from blocker to major.

Thanks for your bug report. I did notice this behaviour on one of my test runs but I couldn't reproduce it. Does it work properly when you restart pybackpack? That might be a workaround but I will need to fix this bug for the next release.

(follow-up: ↓ 3 ) 23/12/07 03:50:25 changed by mochaRHW

Okay, I thought I was doing something wrong, I guess not. To answer your question, no, it does not work properly upon restarting it. Is there a time dependance, like restarting it within a certain period after closing it?

What is it about my system that is causing this? No one else seems to be having this problem..

(in reply to: ↑ 2 ) 23/12/07 12:52:54 changed by Andy

Replying to mochaRHW:

Okay, I thought I was doing something wrong, I guess not. To answer your question, no, it does not work properly upon restarting it. Is there a time dependance, like restarting it within a certain period after closing it?

No, I don't believe that's the case. Though I haven't pinpointed the cause yet.

What is it about my system that is causing this? No one else seems to be having this problem..

I don't think it's your system specifically. I've managed to reproduce the error by creating a new backup set and then trying to back it up straight away. But once pybackpack is restarted, it does find the file list for the backup set in the correct place. I'll fix the bug that I can reproduce and we'll see if it fixes the bug that you're observing also.

23/12/07 16:27:47 changed by Andy

I've just released 0.5.4 so if you could install it and test that the bug is fixed I'll close this ticket.

(follow-up: ↓ 6 ) 23/12/07 20:20:00 changed by mochaRHW

Hey!! It's working!! Thank you!

When you use the first tab to "backup home to a CD" is this going to back up the root user's home or the logged-in user's home? I assume root, since the application runs as super user by default. Can you run the application as a normal user as long as you send the backup to a writable directory?

How does the backup handle symlinks? If I have a symlink to a 200 GB volume in one of the directories that I backup, is the backup going to include the entire contents of the 200 GB volume?

Thanks again!

(in reply to: ↑ 5 ) 23/12/07 20:46:06 changed by Andy

  • status changed from assigned to closed.
  • resolution set to fixed.

Replying to mochaRHW:

When you use the first tab to "backup home to a CD" is this going to back up the root user's home or the logged-in user's home? I assume root, since the application runs as super user by default. Can you run the application as a normal user as long as you send the backup to a writable directory?


It doesn't run as super user by default, not sure what gave you that impression. It should back up whichever home directory is in the user's HOME environment variable.

How does the backup handle symlinks? If I have a symlink to a 200 GB volume in one of the directories that I backup, is the backup going to include the entire contents of the 200 GB volume?


Symlinks are backed up but not followed, so the 200GB volume will not be included in the backup.

I'm closing this ticket now - if you require more support may I suggest using the mailing list ( http://lists.sucs.org/mailman/listinfo/pybackpack ) instead of the bug tracker. Thanks again for testing and filing the bug.