0% found this document useful (0 votes)
17 views4 pages

Design Issues: Naming and Name Resolution

Distributed file systems must address issues related to naming and resolving file locations, implementing caches on clients and servers, and maintaining cache consistency. They must also handle sequential write sharing, availability through replication and failover, scalability to avoid bottlenecks, semantic issues like read behavior, and state management for systems like NFS that use client-side caching.

Uploaded by

waltery2w
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views4 pages

Design Issues: Naming and Name Resolution

Distributed file systems must address issues related to naming and resolving file locations, implementing caches on clients and servers, and maintaining cache consistency. They must also handle sequential write sharing, availability through replication and failover, scalability to avoid bottlenecks, semantic issues like read behavior, and state management for systems like NFS that use client-side caching.

Uploaded by

waltery2w
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Design Issues

Distributed File Systems (contd)


Naming and name resolution

on client or server location-independent or not location-transparent or not

Cache implementations

client, server or both coherent or hints (client) memory or disk write policy

4/11/12

11

Cache consistency

Distributed File Systems (contd)


server-initiated client-initiated driven by the open states of an object using cached info in newly opened files which is outdated

Sequential-write sharing

timestamp file and cache components

4/11/12

22

Distributed File Systems (contd)

Other issues:

Availability

replication and fail-over strategy

Scalability

bottlenecks distribution strategy

Semantics

basic semantics for read latest behavior


33

4/11/12

NFS

Distributed File Systems (contd)


Stateless system not cache coherent uses vnode implementation clients use 3 caches

data names to vnodes file and directory attributes

Sprite Coda (constant data availability) 4/11/12 44

You might also like