The AFS client caches volumename:volumeID# -- when asked to process the mount point it assumed old volumeID#, which no longer existed.
The cache expires every two hours by default, IIRC. In any case, issue "fs checkv" to force an update of the cached name:ID maps, and I suspect that will fix it. Just for conceptual clarity, a mount point contains only the name of the volume to be mounted. That is, it wasn't necessary to delete the mount point, since the newly created mount point contains the same information, i.e. contains the same volume name. Kim On Fri Nov 05 10:04:32 CDT 2010, Thomas Briggs <tbri...@cs.ship.edu> wrote: > Here's the scenario: I had a volume, "user.team1" created, and > mounted on a directory "team1" > > I wanted to purge the files in the account and start with a clean > volume, so : > > --- > fs rmmount team1 > vos remove fs1 a user.team1 > > vos create fs1 a user.team1 > fs mkmount team1 > > --- > > This results in a mount point w/out a device. A vos examine > shows the volume is created, but thats as far as I get. > > Any ideas? > > ------------------------------------------- > Dr. Thomas Briggs, Assoc. Professor > Dept. of Computer Science, Shippensburg University > 1871 Old Main Drive / Shippensburg, PA 17257 / (717) 477-1178 > > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info >