DAFS: Log attempted salvage requests

Log in FileLog (or VolserLog, or the log of any program that requests
salvages) when we request a demand-salvage to occur.

Change-Id: I2444480287a1647c2d3e25039467167e28e17f38
Reviewed-on: http://gerrit.openafs.org/2284
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Reviewed-by: Tom Keiser <tkeiser@sinenomine.net>
Tested-by: Derrick Brashear <shadow@dementia.org>

diff --git a/src/vol/volume.c b/src/vol/volume.c
index 158202e..4f5c86f 100644 (file)
--- a/src/vol/volume.c
+++ b/src/vol/volume.c
@@ -5018,6 +5018,9 @@ static inline int
 try_SALVSYNC(Volume *vp, char *partName, int *code) {
 #ifdef SALVSYNC_BUILD_CLIENT
     if (VCanUseSALVSYNC()) {
+       Log("Scheduling salvage for volume %lu on part %s over SALVSYNC\n",
+           afs_printable_uint32_lu(vp->hashid), partName);
+
        /* can't use V_id() since there's no guarantee
         * we have the disk data header at this point */
        *code = SALVSYNC_SalvageVolume(vp->hashid,
@@ -5036,6 +5039,9 @@ static_inline int
 try_FSSYNC(Volume *vp, char *partName, int *code) {
 #ifdef FSSYNC_BUILD_CLIENT
     if (VCanUseFSSYNC()) {
+       Log("Scheduling salvage for volume %lu on part %s over FSSYNC\n",
+           afs_printable_uint32_lu(vp->hashid), partName);
+
        /*
         * If we aren't the fileserver, tell the fileserver the volume
         * needs to be salvaged. We could directly tell the