[OpenAFS] RO v. RW path not behaving on setup

[Derrick J Brashear]

On Sat, 28 Jun 2003, Steven N. Hirsch wrote:

> At this juncture, 'fs examine' should be showing the *.readonly volumes on
> /afs and /afs/my_cell respectively.  Unfortunately, this does not happen.
> I continue to see the rw volumes on both mount points - even after doing
> fs checkvol.

No it shouldn't. You mounted root.afs, not root.afs.readonly. You get
root.afs.

> When I attempt to stop AFS, 'umount' causes a kernel oops and the AFS
> client daemons refuse to shut down.  After rebooting the server,
> everything _seems_ to look right!  Both /afs and /afs/my_cell show up as
> being the *.readonly variants.  But, now I am unable to get proper RO/RW
> pathing behavior.

I've seen this bug but it went away when I switched to a newer kernel;
What are you running?

> Example: I create a volume called my_cell.users, mount it under
> /afs/.my_cell and release it.  It then shows up under /afs/my_cell, but
> acts as an RO volume - the cache manager does not follow the correct path
> on writes.  I've removed all volumes and retried this sequence several
> times with exactly the same results.

That sounds like how it's supposed to work. /afs/my_cell is RO, you make
an RO, you get an RO. You want writes, you do into /afs/.my_cell, or you
donm't replicate the volume.

> I hate to wipe the entire AFS server install and start from scratch.  Can
> anyone provide even a guess as to what's wrong?