[OpenAFS] Re: Writing allowed where it's not expected

[Andrew Deason]

On Sun, 18 Sep 2011 10:20:05 +0200
Dirk Heinrichs <dirk.heinrichs@altum.de> wrote:

> The only thing I did was to "vos release" _another_ volume that was
> mounted below .../sw and which showed up as "not released" in the
> output of "vos listvldb". Does this also count as "being on a
> read/write path"?

Yes. You can usually pretty quickly see which volume is causing the
"read-write path"-ness by running 'fs exa' or 'fs lq' on each parent
directory starting with /afs/ and working your way down.

-- 
Andrew Deason
adeason@sinenomine.net