How do local file systems compare to distributed file systems in metadata management and latency?

• A. Local file systems store metadata remotely, while distributed store metadata locally.
• B. Local file systems store metadata locally, while distributed file systems rely on metadata servers and distributed data.
• C. Distributed file systems store all data on a single node.
• D. Local file systems do not manage metadata.

Answer: (B)

The main idea is how and where file metadata is stored and how that affects latency. In a local file system, the metadata—things like directory entries, permissions, ownership, and the mapping from a file name to its storage location—is kept on the same machine, typically on the local disk and in memory caches. That means metadata lookups are fast, because they don’t need to travel over a network and can be satisfied quickly from the local file system structures.

In a distributed file system, metadata is managed by dedicated metadata servers. The namespace and the mapping from file paths to where data blocks live are handled by these servers, which may be centralized or distributed across multiple nodes. When a client accesses a file, it usually first contacts the metadata service to locate the data blocks, then retrieves the data from storage nodes across the cluster. This introduces network latency for metadata operations, but it enables scalable, fault-tolerant storage where data is spread across many machines.

So the statement that matches this behavior is that local file systems store metadata locally, while distributed file systems rely on metadata servers and distributed data.