[OpenAFS] Writing allowed where it's not expected

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig09820A4BED072D0D64AE5194
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 9/17/2011 5:23 AM, Dirk Heinrichs wrote:
> Hi,
>=20
> I currently observe a strange behavior where I can write to a volume
> although I am on a read-only path, like:
>=20
> % pwd
> /afs
> % fs lsm altum.de
> 'altum.de' is a mount point for volume '#altum.de:root.cell'
> % fs lsm .altum.de
> '.altum.de' is a mount point for volume '%altum.de:root.cell'
> % cd altum.de    =20
> % fs lsm sw
> 'sw' is a mount point for volume '#sw'
> % vos listvol rohan a |grep sw
> sw                                536871302 RW          4 K On-line
> sw.readonly                       536871303 RO          3 K On-line
> % ll sw/foo
> zsh: no such file or directory: sw/foo
> % touch sw/foo
> % ll -g -n sw/foo            =20
> -rw------- 1 100 0 2011-09-17 11:14 sw/foo
>=20
> Shouldn't the write operation be prevented, since I am on a read-only
> path?
>=20
> Bye...

fs exa /afs/altum.de/sw

what version of openafs on what operating system?



--------------enig09820A4BED072D0D64AE5194
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJOdGklAAoJENxm1CNJffh4/rsIAJWyae4JHFCQsQ30OhzeDDfE
yGL8OyxwVeiblXDAQCWU/UO8FjmaTKNYpiRNHj0ZT5Gn0iPsQGYwI6HpKhP0yzDU
DJ9chmvDdPbDFWmH5DW7ULqSC1sMjNQToiRvPr1e0DDiTF6tborXCpwNCHFipOZk
T9enI+ku+x2PlQW4oUUUnbRoS9PwrpNhGgbjTE51a/yjFr2nO3Dha9c+gUcLCoqR
LpNwcN2+AZc1WAdY6lCsOY31XA5UO4XRoXYkBw3n5ulUPTT/yjAavdteyUq9MmmR
U1FlIHfFPJRbdMLCfwOE5/qM/mfe05/LjKNXa6fJBfMIHdM7ffo/Scp9e2Mvei4=
=43MY
-----END PGP SIGNATURE-----

--------------enig09820A4BED072D0D64AE5194--