vos: noise messages when attempting to delete non-existent volume
authorMark Vitale <mvitale@sinenomine.net>
Thu, 7 Mar 2013 14:34:55 +0000 (09:34 -0500)
committerStephan Wiesand <stephan.wiesand@desy.de>
Wed, 17 Apr 2013 12:10:29 +0000 (05:10 -0700)
commitddaef4378de7af439de1d574155506f659ca8c56
tree4290f7a2a09b7b8d0e9e2cd2da622acac30c3609
parent1c811f9fddf336317099e7ec73e28131acf65be8
vos: noise messages when attempting to delete non-existent volume

With vos refactor commit f4e73067cdef990262c69c38ac98761620a63f25,
some formerly conditional volume deletes are now unconditional.
This regresses 'vos move' output with harmless "error" messages
when AFSVolTransCreate() returns VNOVOL:
  "Failed to start transaction on <volume>"
  "Volume not attached, does not exist, or not online"

Modify DoVolDelete() to return early (and silently) with VNOVOL
in this case, allowing the caller to handle this appropriately.

Reviewed-on: http://gerrit.openafs.org/9596
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
(cherry picked from commit 1092cbe34fc8519826b3fa0565505b7bd81bc922)

Change-Id: I77e701378a999c8ad9413bfefcace0ee06aecb07
Reviewed-on: http://gerrit.openafs.org/9597
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Simon Wilkinson <simonxwilkinson@gmail.com>
Reviewed-by: Derrick Brashear <shadow@your-file-system.com>
src/volser/vsprocs.c