Hola Carles,
> We updated our WNs to CVMFS 2.1.15 from CVMFS 2.0.22.
Note: a live upgrade from 2.0 to 2.1 is not supported.
> [...]
>
> However, we did not want to wipe all the cached CVMFS directories since there were
> only one or two repositories failing per WNs, not all. We found that, unmounting the
> problematic repositories (using "-l" option) and rerunning cvmfs_config probe again,
> we solved the problem for the major part of the WNs, [...]
That is a good recipe for dealing with such issues, should they occur.
With 2.1.15 and later versions the need for admin interventions ought
to become rarer...
|