[OpenAFS] Re: [Slightly OT] changing UID of a user to 1 ["readonly mountpoint"]
Dexter 'Kim' Kimball
Mon, 29 Aug 2005 15:06:51 -0600
The "readonly mountpoint" nomenclature is widely used to mean "#" =
mountpoint but is inaccurate.
A read-only mountpoint is created with "fs mkmount <dir> =
and results in a regular (#) mountpoint and takes you to a readonly =
A _regular_ mountpoint is created with "fs mkmount <dir> volname" and
results in a mountpoint with # but takes you to a readwrite volume or a
readonly volume depending on the cache manager's "Volume Traversal =
The Volume Traversal Rules are applied at each mount point the AFS =
1. At a regular (#) mountpoint, if ".readonly" is used in the named =
go to a .readonly instance of the volume. If none exists, fail.
2. At a regular (#) mountpoint, if ".backup" is used in the named volume =
to the .backup instance of the volume. If none exists, fail.
3. At a regular (#) mountpoint:
a. If currently in a readonly volume and the VLDB indicates that a
readonly instance exists for the volume named in the mount point, go to =
readonly instance or fail.
b. If currently in a readwrite volume go to the readwrite instance =
the volume named in the mount point, or fail. Replicas and .backup =
3. At a readwrite (%) mountpoint, go to the readwrite instance of the =
named in the mount point, or fail. Replicas and .backup volumes are
Kim (Dexter) Kimball
> -----Original Message-----
> From: firstname.lastname@example.org=20
> [mailto:email@example.com] On Behalf Of Jeffrey Altman
> Sent: Monday, August 29, 2005 1:08 PM
> To: Russ Allbery
> Cc: Madhusudan Singh; firstname.lastname@example.org
> Subject: Re: [OpenAFS] Re: [Slightly OT] changing UID of a user to 1
> The '#' means that the mount point is a read-only path.
> If it were a read-write path, there would be a '%'.
> Jeffrey Altman
> Russ Allbery wrote:
> > Madhusudan Singh <email@example.com> writes:
> >>Indeed it was an lsmount in my script (included as a=20
> check). And then
> >>adduser was failing with a force-badname check. Fixed that,=20
> deleted bnl4
> >>from the admin group and am now back in business.
> >>In any case, what does the # mean above.
> > It's an artifact of how AFS internally represents mount points. The
> > actual volume name is the name omitting the #. It's confusing, but
> > changing it at this point would probably break other things.