The Crash Consistency Problem
Hopefully, from these crash scenarios, you can see the many problems
that can occur to our on-disk file system image because of crashes: we can
have inconsistency in file system data structures; we can have space leaks;
we can return garbage data to a user; and so forth. What we’d like to do
ideally is move the file system from one consistent state (e.g., before the
file got appended to) to another atomically (e.g., after the inode, bitmap,
and new data block have been written to disk). Unfortunately, we can’t
do this easily because the disk only commits one write at a time, and
crashes or power loss may occur between these updates. We call this
general problem the crash-consistency problem (we could also call it the
Do'stlaringiz bilan baham: |