[OpenAFS] Writing allowed where it's not expected

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


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 18.09.2011 09:47, schrieb Dirk Heinrichs:
> Am 17.09.2011 17:51, schrieb Jeffrey Altman:
> 
>> And is the sw.readonly volume accessible?
> 
> Yes, I think so.
> 
>> vos examine sw.readonly -cell altum.de
> 
> sw.readonly                       536871303 RO          3 K
> On-line rohan.altum.de /vicepa RWrite  536871302 ROnly  536871303
> Backup          0 MaxQuota       5000 K Creation    Sat Sep 17
> 09:41:04 2011 Copy        Sat Sep 17 09:41:04 2011 Backup
> Never Last Access Sat Sep 17 09:40:59 2011 Last Update Sat Sep 17
> 09:40:59 2011 0 accesses in the past day (i.e., vnode references)
> 
> RWrite: 536871302     ROnly: 536871303 number of sites -> 2 server
> rohan.altum.de partition /vicepa RW Site server rohan.altum.de
> partition /vicepa RO Site
> 
> Is it because both are on the same partition? I guess not...

Hmm, for some reason not entirely clear to me, it now works as expected.

% pwd
/afs/altum.de
% touch sw/foo
touch: cannot touch `sw/foo': Read-only file system
% cd ../.altum.de
% touch sw/foo
% ll -g -n sw/foo
- -rw------- 1 100 0 2011-09-18 10:16 sw/foo
% cd -
/afs/altum.de
% ll -g -n sw/foo
ls: cannot access sw/foo: No such file or directory
% vos release sw
Released volume sw successfully
% ll -g -n sw/foo
- -rw------- 1 100 0 Sep 18 10:16 sw/foo

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"?

Bye...

	Dirk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOdam18NVtnsLkZ7sRAgAUAJ9tan2EpjircwslV3mS6mVHiPbRQACeORGK
NeWbmq+mol5Ed4N2eYFW7io=
=EvFb
-----END PGP SIGNATURE-----