OK I won't set it to fixed then! We have to think about another solution then.
The problem mainly is how to recognise a mounted network share from a normal
folder, before testing whether it is mounted or not...
(same procedure for other mounted devices btw)
** Changed in: backintime
Importance: Undecided => Medium
** Changed in: backintime
Status: New => Confirmed
--
backintime hangs w/o network presence of previously backedup network share
https://bugs.launchpad.net/bugs/477603
You received this bug notification because you are a member of Back In
Time Team, which is subscribed to Back In Time.
Status in Back In Time: Confirmed
Bug description:
Using backintime 0.9.26-3 it's 100% reproducible here on an up to date new
install of Ubuntu 9.10 networked with a winXP laptop which has a share visible.
Goal: backup linux machine and winxp share to an ext4 partition on an esata
portable drive
The windows share is visible as /home/xxxx/.gvfs/yyyy on toshiba/
default settings are used except for:
exclude_patterns=*.backup*:*~:.cache*:[Cc]ache*:.thumbnails*:[Tt]rash*
include_folders=/home/xxxx|0:/etc|0
----- How to demonstrate the behavior -----
With the two machines networked, take several backups. They are successful and
include the winxp share.
Later, take the winxp box off the network and take another snapshot.
backintime hangs permanently with the message "Working: Save permission ..."
At that point, 'new_snapshot' exists (as seen in Nautilus but not in
backintime's Snapshots sidebar) and is populated with files but fileinfo.bz2 is
empty.
While backintime is hung, reconnect the winxp box to the network.
backintime then writes to fileinfo.bz2, renames the snapshot to the date/time
formula, completing the backup.
------
This behavior can be eliminated by adding '/home/xxxx/.gvfs' to
exclude_patterns.
Then a new snapshot can be successfully started and completed.
It looks like backintime's default excluding of dot.files masked this behavior.
I consider it to be a problem since I want to backup that share when its
available and I don't want its presence to be a necessary condition for
unattended backups of the linux box.
_______________________________________________
Mailing list: https://launchpad.net/~bit-team
Post to : bit-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~bit-team
More help : https://help.launchpad.net/ListHelp
