You are here. See how this question connects to other ideas.
Select a node to open its page · Expand to read within the map
One question
Where does a mount put a resource?
An entry path and the resource’s original location are different things.
A task needs access to a report service without knowing its internal directories or network address. A mount gives those resources an AFS entry point and identifies the Provider that connects them.
Suppose the service contains a weekly report. Mounting it at the illustrative entry /reports lets a consumer address /reports/weekly. Three roles remain distinct:
| Role | Question | Example |
|---|---|---|
| Mount location | Where do I enter from this environment? | /reports |
| Provider | Who connects operations to resources? | The report-service adapter |
| Underlying resource | What is actually read or changed? | The service’s weekly report |
This does not require copying the entire service into disk files. The common interface supplies access and operations; a remote service can continue managing the resource.
Two tasks can receive different arrangements. One may have full reports while another receives public summaries. Comparing path strings alone is insufficient: inspect what each environment mounts and permits.
When a read fails, first establish which resource the entry refers to in this environment. Then distinguish a missing resource, unsupported operation and denied access.
Go deeper
Check your understanding
Must mounting a service copy its data into disk files?
No. A mount establishes the entry point; its Provider can connect operations to resources still managed by a remote service.