Why can volcreate modify the mountpoint database but volnuke cannot?

[macrotex]

We use volcreate and volnuke to manage our AFS volumes. The volcreate command will, if the $LOADMTPT variable is set, run the program pointed to by $LOADMTPT thereby allowing the updating of the mountpoint database on volume create. That is very helpful.

However, volnuke does not remove the mountpoint database entry. This causes us a problem in that now we have mountpoint entries pointing to non-existent volumes.

Question: why doesn't the volnuke have a similar facility?

[whm]

I take this as a feature request. I won't be able to look at this for a couple weeks.

[whm]

Note, there are two conditions here: 1)volnuke is supplied with a mountpoint or 2) volnuke is supplied with a volume id. Because of this is makes sense to me to implement separate configuration variables to cover both conditions. I propose adding the variables $UNLOADMTPT and $VOLNUKEPOST. $UNLOADMTPT would be executed only if it is specified and a mount point is specified on the command line. $VOLNUKEPOST would attempt to be executed if it is non-null.

[macrotex]

A mountpoint database record contains the mountpoint path, volume name, and volume id. Thus even if only the volume id is supplied to volnuke the mountpoint database can be updated. My suggestion is, in the same way that volcreate works, if $LOADMTPT is not empty use it to delete all rows of the mountpoint database (almost always this will be zero or one) that match the volume id supplied to volnuke. I don't think the $VOLNUKEPOST is necessary.

See also https://www.eyrie.org/~eagle/notes/afs/afsdb.html

[jaltman]

If the volume location entry is being removed, then there are three volume ids which are being deleted. The RW ID, RO ID and BACK ID. There can be mountpoints referring to all of them. I would suggest that if volnuke is removing the volume location entry, then it should remove any "mountpoint database" records which reference any of the three volume ids.

[jaltman]

volnuke when called with the -m switch will fetch the target of a mount point and use that a the source of the volume name. It will then remove the mountpoint itself at the end of the operation. Currently this is performed using "fs lsmount" and "fs rmmount". AuriStor will add "afsio lsmount" so that it and "afsio rmmount" can be used when a cache manager is not present.