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)
committerDerrick Brashear <shadow@your-file-system.com>
Wed, 13 Mar 2013 16:49:25 +0000 (09:49 -0700)
commit1092cbe34fc8519826b3fa0565505b7bd81bc922
tree0cb03f431b2ee09eaacbc20946e1ff6240d7c678
parentbb42c02ce56aec29e3860bec47e47157d0406f20
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.

Change-Id: I21a72e38f330335adf97ac50a7ac7d0fb97c1a9c
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>
src/volser/vsprocs.c