OpenAFS Master Repository branch, openafs-stable-1_8_x, updated. openafs-stable-1_8_6-61-g27a2cda
Gerrit Code Review
gerrit@openafs.org
Fri, 20 Nov 2020 14:41:00 -0500
The following commit has been merged in the openafs-stable-1_8_x branch:
commit 27a2cdadd221d4a870d5ce9b936bb103c605cafb
Author: Andrew Deason <adeason@sinenomine.net>
Date: Mon Nov 12 15:01:18 2018 -0600
vlserver: Warn when we cannot unhash deleted entry
If we are trying to delete an entry from the vldb, we fail with
VL_NOENT if we cannot find the given entry on one of its hash chains.
This is indicative of corruption in the vldb (since we have an entry
not on a hash chain), but we don't really indicate this clearly. There
are no log messages, and the user running 'vos' only sees an error
like this:
$ vos delentry 123456
Could not delete entry for volume 123456
You must specify a RW volume name or ID (the entire VLDB entry will be deleted)
VLDB: no such entry
Deleted 0 VLDB entries
Which is the exact same error message if the user tries to delete a
volume that does not actually exist.
We currently do not have an error code that clearly says that the
database appears corrupted and needs to be fixed, but we can at least
log an error in VLLog for this case, to give the administrator a
chance at fixing the situation. So, log a message in this situation.
Reviewed-on: https://gerrit.openafs.org/13382
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
(cherry picked from commit 3e3fce24da31a31ca9a3f4ad356c4e4eaf0ad897)
Change-Id: Ia76c5d7a19c3d21a89fc502e14922672afd8a84f
Reviewed-on: https://gerrit.openafs.org/14434
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Cheyenne Wills <cwills@sinenomine.net>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
src/vlserver/vlutils.c | 19 +++++++++++++++++--
1 files changed, 17 insertions(+), 2 deletions(-)
--
OpenAFS Master Repository