Difference between revisions of "Operating Systems 2014F Lecture 14"
(Created page with "How does an operating system know it's accessed memory it doesn't have access to? A lot of you said segments. Filesystems - normally operating system mechanisms are talkin...") |
(No difference)
|
Revision as of 09:52, 5 November 2014
How does an operating system know it's accessed memory it doesn't have access to? A lot of you said segments.
Filesystems - normally operating system mechanisms are
talking about access to hardware systems, persistent storage. - abstraction for persistent storage. Storage that maintains it's state when it loses power. A couple of challenges with persistent storage. What's weird about storing things in persistent storage? It's slow. durability and persistent.
Going to make errors - we should be able to recover from them. Maybe not fix everything, but preserve most of the data. This is a huge burden on filesystems. Filesystem development tends to be very slow in practise. Whatever code you have doing this, has to do this right. Older filesystems tend to be more trustworthy, when hardware changes, bugs you didn't know where in the filesystem may come up.