The Design and Implementation of a Log-Structured File System

All data structures in LFS are written to the log. The inode map contains locations of the inodes, the inodes contain the location of the data blocks. This is followed for both files and directories (which are just special files whose data consists of file names and inode numbers within that directory). The checkpoint region (not shown in this image) stores the location of the blocks of the inode map and is stored at a fixed location on the disk. However, the checkpoint region is updated lazily. By storing all the data structures in the log (and ensuring that the one structure not in the log is written to lazily), LFS is able to (almost) always write to the disk in large sequential segments.




Visit for summaries of computer science research papers.

Love podcasts or audiobooks? Learn on the go with our new app.

Partitioning in Spark

AWS Deep Learning Containers Are Awesome 🙌

Deploy decisions to DMN Developer Sandbox

How to secure WebLogic JMS Resources?

MetaHIVE Community Update

Create your own vision alerting system with IoT Edge, Azure Custom Vision and a Jetson Nano

Don’t let the virus kill your developers' learning experience

Importing the variable files based on the OS family in the Ansible Playbook

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Rajat Kateja, After Hours Academic

Rajat Kateja, After Hours Academic

Visit for summaries of computer science research papers.

More from Medium

Container-Diff: Change Management for Containers

My Engineering Journey at Midtrans: Addressing Problems One Step at A Time

API Economy- Why You Should Be A Part Of It

Relational to NoSQL. Transformation of databases!