From: Andrew Deason Date: Wed, 8 Dec 2010 20:57:13 +0000 (-0600) Subject: DAFS: Avoid logging harmless LEAVE_OFF failures X-Git-Tag: upstream/1.8.0_pre1^2~4371 X-Git-Url: https://git.michaelhowe.org/gitweb/?a=commitdiff_plain;h=f88c91f7778b9a8bf920dce08ccab76ac0b1b433;p=packages%2Fo%2Fopenafs.git DAFS: Avoid logging harmless LEAVE_OFF failures The DAFS volserver can create temporary destroyMe volumes, which it then tells the fileserver to keep offline with an FSYNC_VOL_LEAVE_OFF message. When the fileserver doesn't know that the volume exists, currently it responds with SYNC_DENIED, which causes the volserver to log the error with a "negative response on circuit FSSYNC" message. These are harmless, though, since leaving a volume offline that the fileserver does not know about is a no-op. So return the SYNC_FAILED code instead, which does not get logged, and is more consistent with some other FSYNC handlers like FSYNC_VOL_DONE. Change-Id: I315d091fb419767ae33c1846d90e5ef83372477d Reviewed-on: http://gerrit.openafs.org/3494 Reviewed-by: Derrick Brashear Tested-by: Derrick Brashear --- diff --git a/src/vol/fssync-server.c b/src/vol/fssync-server.c index b9bb6e6c8..56bac3c04 100644 --- a/src/vol/fssync-server.c +++ b/src/vol/fssync-server.c @@ -742,7 +742,7 @@ FSYNC_com_VolOn(FSSYNC_VolOp_command * vcom, SYNC_response * res) res->hdr.reason = FSYNC_WRONG_PART; } } else { - code = SYNC_DENIED; + code = SYNC_FAILED; res->hdr.reason = FSYNC_UNKNOWN_VOLID; } #endif