wting / flyback

Automatically exported from code.google.com/p/flyback
0 stars 0 forks source link

available snapshot list not updating. #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. install a new version of FlyBack
2. try to set the storage location at a directory on a partition of a local
disk
3. storage location shows (none) as location instead of the directory

What is the expected output? What do you see instead?
(none) in the dropdownlist instead of the path

What version of the product are you using? On what operating system?
0.2.1 on kubuntu g. 

Please provide any additional information below.
The console outputs:
$ rsync -av --delete '/home/okke/' '/media/sda3/backuptest/2007-11-07
19:46:05/home/okke/'
building file list ... done
rsync: mkdir "/media/sda3/backuptest/2007-11-07 19:46:05/home/okke" failed:
No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(529) [receiver=2.6.9]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(454)
[sender=2.6.9]

This might be because of this bug. It might be another bug.

Original issue reported on code.google.com by okke.formsma on 7 Nov 2007 at 6:55

GoogleCodeExporter commented 9 years ago
this snapshot might help

Original comment by okke.formsma on 7 Nov 2007 at 7:02

Attachments:

GoogleCodeExporter commented 9 years ago
it looks like your storage location is being set.  did
"/media/sda3/backuptest/2007-11-07 19:46:05/home/okke" get created?

Original comment by pub...@kered.org on 7 Nov 2007 at 10:12

GoogleCodeExporter commented 9 years ago
The directory does not get created.

The console in which I run flyback.py outputs 

mkdir: cannot create directory `/media/sda3/backuptest/2007-11-07 23:54:43': 
Invalid
argument
mkdir: cannot create directory `/media/sda3/backuptest/2007-11-07 23:54:43': 
Invalid
argument
chmod: cannot access `/media/sda3/backuptest/2007-11-07 23:54:43': No such file 
or
directory

After rebooting the program, it lists my default location in the dropdown-box as
'backuptest', so that does work now. Strange it didn't update right in the 
first place.

However, the program still can't create a directory. I checked, and it does have
permissions to create a directory.

The built-in console outputs the following if I try to run a backup:

$ rsync -av --delete '/lib/' '/media/sda3/backuptest/2007-11-07 23:54:43/lib/'
building file list ... done
rsync: mkdir "/media/sda3/backuptest/2007-11-07 23:54:43/lib" failed: No such 
file or
directory (2)
rsync error: error in file IO (code 11) at main.c(529) [receiver=2.6.9]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(454) 
[sender=2.6.9]

Original comment by okke.formsma on 7 Nov 2007 at 11:02

GoogleCodeExporter commented 9 years ago
in svn, all commands now get outputed to the output box.  can you run again and 
show
the error the mkdir is throwing?

Original comment by pub...@kered.org on 8 Nov 2007 at 12:38

GoogleCodeExporter commented 9 years ago
I'm sorry, I spotted the problem: my filesystem on the second disk is FAT. And 
FAT
does not support a semicolon in the filename... Oops!

So, after running it on my ext3 disk, it can create backups. But then I get 
another
error: 'error2'. The list of system snapshots in the main screen only shows 
'now' and
doesn't update. The directories do get created and filled...

Original comment by okke.formsma on 8 Nov 2007 at 10:45

Attachments:

GoogleCodeExporter commented 9 years ago
"error2" isn't really an error, was just a debug statement i've since removed.

odd that it didn't refresh the backup list.  can you add a print statement to
"refresh_available_backup_list" to see if it gets called?

how about if you quit and restart?  do they show then?

also, i see you're using KDE....is it still gnome handling the drawing or are 
you
using one of those gnome2kde wrappers?

Original comment by pub...@kered.org on 8 Nov 2007 at 9:18

GoogleCodeExporter commented 9 years ago

Original comment by pub...@kered.org on 11 Nov 2007 at 9:28

GoogleCodeExporter commented 9 years ago
Strange, the latest SVN version, 42, is working correctly on my PC now. I have 
no
clue what has caused the problem... I'm sorry for the inconvenience!

Original comment by okke.formsma on 12 Nov 2007 at 11:13

GoogleCodeExporter commented 9 years ago
not a problem.  thanks for using/testing.  :)

Original comment by pub...@kered.org on 12 Nov 2007 at 6:36