Very very odd behavior. To put it in short.. an entire fileserver's RW volumes became unavailable to our colo sites, but not the local site. Every effort to determine the cause was met with frustration (all sorts of cachemanager operations yielded nothing)
That is, until I did an fs whereis on the affected volume, on the fileserver machine itself... It told me the RW volume was available on host 192.168.122.1. Formerly a virtual host bridge interface, but no longer used. VLDB did not show this.. syncserv and syncvldb's had not fixed the problem. Restarting the fileserver process did not release it, even though the IP was no longer active. So I moved one volume. That worked. But I didn't want to do that for the entire fileserver. So I entered -rxbind to the fileserver process and restarted it. Voila. Problem solved. -- Timothy Balcer / IT Services Telmate / San Francisco, CA Direct / (415) 300-4313 Customer Service / (800) 205-5510
