| 2009-08-12 12:02:07 |
Mark Baas |
bug |
|
|
added bug |
| 2009-08-20 10:59:56 |
Borph |
summary |
hardlinking not working in cronned snapshots |
hardlinking doesnt work from cronjob with schedule per included folder enabled |
|
| 2009-08-27 08:45:59 |
Bart de Koning |
backintime: status |
New |
Incomplete |
|
| 2009-09-01 12:30:24 |
Bart de Koning |
backintime: status |
Incomplete |
Confirmed |
|
| 2009-09-01 12:31:09 |
Bart de Koning |
summary |
hardlinking doesnt work from cronjob with schedule per included folder enabled |
hardlinking doesnt work with schedule per included folder enabled |
|
| 2009-09-01 12:39:14 |
Bart de Koning |
description |
I have my snapshot folder on a ext4 formatted memory card.
The snapshots are too big, without changing anything the snapshot size is the size of the folder, so i assume hardlinking is not working. However in the gnome gui when pressing the manual copy button, the final size is quite normal, not more than 4 mb. |
Schedule per included folder is BUGGY, do NOT use it unless you want to do some debugging or if you have plenty of space (and computing power)!
The snapshots are too big, also without changing anything the snapshot size is the size of the folder, so hardlinking is not working. For the tasks with higher frequency the hardlinking fails: consuming the full space of all the folders that are scheduled for backup (also the ones with lower frequencies). The time to make the snapshot is incredibly long (exceeding 10 times the time to create a normal complete snapshot, which is logical as it recreates every single bit)
The lowest frequency tasks and manual backups behave normally |
|
| 2009-09-02 10:42:11 |
Bart de Koning |
backintime: assignee |
|
Bart de Koning (bratdaking) |
|
| 2009-09-02 11:54:30 |
Bart de Koning |
branch linked |
|
lp:~bratdaking/backintime/bug-412470 |
|
| 2009-09-03 09:10:32 |
Bart de Koning |
backintime: status |
Confirmed |
Fix Committed |
|
| 2009-09-24 12:02:03 |
kanub |
backintime: status |
Fix Committed |
Fix Released |
|
| 2009-09-24 12:02:10 |
kanub |
backintime: status |
Fix Released |
Fix Committed |
|
| 2009-09-24 13:43:11 |
Bart de Koning |
backintime: importance |
Undecided |
High |
|
| 2010-07-05 13:48:09 |
Alessandro Cuttin |
description |
Schedule per included folder is BUGGY, do NOT use it unless you want to do some debugging or if you have plenty of space (and computing power)!
The snapshots are too big, also without changing anything the snapshot size is the size of the folder, so hardlinking is not working. For the tasks with higher frequency the hardlinking fails: consuming the full space of all the folders that are scheduled for backup (also the ones with lower frequencies). The time to make the snapshot is incredibly long (exceeding 10 times the time to create a normal complete snapshot, which is logical as it recreates every single bit)
The lowest frequency tasks and manual backups behave normally |
Schedule per included folder is BUGGY, do NOT use it unless you want to do some debugging or if you have plenty of space (and computing power)!
The snapshots are too big, also without changing anything the snapshot size is the size of the folder, so hardlinking is not working. For the tasks with higher frequency the hardlinking fails: consuming the full space of all the folders that are scheduled for backup (also the ones with lower frequencies). The time to make the snapshot is incredibly long (exceeding 10 times the time to create a normal complete snapshot, which is logical as it recreates every single bit)
The lowest frequency tasks and manual backups behave normally
|
|
| 2010-09-12 19:28:14 |
Dan |
backintime: status |
Fix Committed |
Fix Released |
|
