- 2075 Bhadra · 5 marks
GFS vs other file systems
Short answer
GFS differs by expecting failures on commodity hardware, using 64 MB chunks, favoring large streaming reads and append writes, separating a metadata master from direct client-to-chunkserver data flow, and providing relaxed consistency with replication and atomic record append rather than strong POSIX semantics.
How GFS differ from other File Systems? List out five distinct differences.
GFS was designed around Google's workload and failure assumptions, so it differs from traditional file systems (such as NFS, ext, NTFS or AFS) in these ways.
| Point | GFS | Traditional file systems |
|---|---|---|
| Hardware | Thousands of cheap commodity machines; failures are normal | Reliable, costly hardware; failure is rare |
| Chunk/block size | Very large, 64 MB chunks | Small blocks (4 KB to 64 KB) |
| File size and workload | Multi-GB files, large streaming reads, append-mostly writes | Many small files, random read/write |
| Architecture | Single master for metadata, chunkservers for data, clients talk directly to chunkservers | Often tightly coupled server (NFS) or no separate metadata service |
| Fault tolerance | Each chunk replicated (3 copies), checksums, automatic re-replication | Relies on RAID or backups, limited replication |
| Consistency | Relaxed consistency, atomic record append | Strong POSIX semantics |
| Caching | No client data cache (files too large); metadata cached | Data caching is common |
| Interface | Custom API with snapshot and record append, not fully POSIX | Standard POSIX interface |
Five distinct differences in brief: (1) commodity hardware with constant failures expected, (2) 64 MB chunks, (3) append-oriented large-file workload, (4) separate metadata master with direct client-chunkserver data flow, (5) built-in replication with a relaxed consistency model and atomic record append.
✓ Answer checked by Claude Opus 5.5 (high effort)
Related questions
- Google File System architecture · Big Data Technologies, chapter 2 · asked 2×
- Availability and fault tolerance in GFS · Big Data Technologies, chapter 2
- Column vs row-oriented NoSQL databases · Big Data Technologies, chapter 4
- GFS vs HDFS architecture · Information System, chapter 8
- Microwave vs low frequency and five system protocols · RF and Microwave Engineering, chapter 1
- File attributes; directory systems; free blocks · Operating System, chapter 5
- File system layout; interface vs implementation · Operating System, chapter 5