Fix #5461 #5513 #4717 About WroteVol non-zero message

When this message is printed, we have seen data corruptions on
volumes that are currently mounted. This patch should prevent
that situation to happen.

diff --git a/bacula/src/stored/mount.c b/bacula/src/stored/mount.c
index c0e89e09ec5c98eefc71de27e59658fe068a6f83..4a00b02186f1c8edbf71b45b02f15f276486c145 100644 (file)
--- a/bacula/src/stored/mount.c
+++ b/bacula/src/stored/mount.c
@@ -262,7 +262,14 @@ read_volume:
       if (!find_a_volume()) {
          goto mount_next_vol;
       }
-      dev->set_volcatinfo_from_dcr(this);
+      if (strcmp(dev->VolHdr.VolumeName, dcr->VolCatInfo.VolCatName) == 0) {
+         dev->set_volcatinfo_from_dcr(this);
+
+      } else {      /* We have a volume, but not the current one */
+         Dmsg2(5, "Will need to re-mount volumes %s %s\n",
+               dev->VolHdr.VolumeName, dcr->VolCatInfo.VolCatName);
+         goto mount_next_vol;
+      }
    }
 
    /*