kes Implement code that should properly set that a job was migrated,

[bacula/bacula] / bacula / kernstodo

diff --git a/bacula/kernstodo b/bacula/kernstodo
index 4571380e34f593dc52a9bc25117b49aae3f495f8..8a541ed63c471f0847cf1963d7a62a7d60ec6135 100644 (file)
--- a/bacula/kernstodo
+++ b/bacula/kernstodo
@@ -41,13 +41,11 @@ Document:
  
 
 Priority:
+- Check if gnome-console works with TLS.
 - Ensure that the SD re-reads the Media record if the JobFiles
   does not match -- it may have been updated by another job.
 - Look at moving the Storage directive from the Job to the
   Pool in the default conf files.
-- Make sure the new level=Full syntax is used in all 
-  example conf files (especially in the manual).
-- Fix prog copyright (SD) all other files.
 - Migration Volume span bug
 - Rescue release
 - Bug reports
@@ -59,11 +57,12 @@ Priority:
 - Wrong jobbytes with query 12 (todo)
 - bacula-1.38.2-ssl.patch
 - Bare-metal recovery Windows (todo)
-- Document need for UTF-8 format
 
 
 
 For 1.39:
+- Fix hardlinked immutable files when linking a second file, the
+  immutable flag must be removed prior to trying to link it.
 - Implement Python event for backing up/restoring a file.
 - Change dbcheck to tell users to use native tools for fixing
   broken databases, and to ensure they have the proper indexes.
@@ -92,6 +91,20 @@ For 1.39:
   .move transfer device=xxx fromslot=yyy toslot=zzz
 
 Low priority:
+- It appears to me that you have run into some sort of race
+  condition where two threads want to use the same Volume and they
+  were both given access.  Normally that is no problem.  However,
+  one thread wanted the particular Volume in drive 0, but it was
+  loaded into drive 1 so it decided to unload it from drive 1 and
+  then loaded it into drive 0, while the second thread went on
+  thinking that the Volume could be used in drive 1 not realizing
+  that in between time, it was loaded in drive 0.
+  I'll look at the code to see if there is some way we can avoid
+  this kind of problem.  Probably the best solution is to make the
+  first thread simply start using the Volume in drive 1 rather than
+  transferring it to drive 0.
+- After pruning, check to see if the Volume retention period has
+  expired.
 - Check to see if jcr->stime is lost during rescheduling of
   jobs in jobq.c
 - Fix re-read of last block to check if job has actually written
@@ -1735,3 +1748,7 @@ Block Position: 0
 - Make release unload any autochanger.
 - Arno's reservation deadlock.
 - Eric's SD patch
+- Make sure the new level=Full syntax is used in all 
+  example conf files (especially in the manual).
+- Fix prog copyright (SD) all other files.
+- Document need for UTF-8 format