Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Well, I can't say that I haven't given it a try, but I really don't know that much about computers so I'm not really sure what these sources are talking about. I do understand, however, that designers have tried to make it so that reading data is done from RAM, while writing is done directly to disk. Can someone explain why things are this way, and sort of the high-level pictures of how Write-Anywhere File Systems work?

share|improve this question

closed as not a real question by MikeyB, Steven Monday, Mark Henderson Oct 14 '11 at 3:41

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Basically, why does the "write-anywhere" make writes any faster? I thought sequential writes were always faster than "writing anywhere"... – Dark Templar Oct 14 '11 at 2:42
up vote 0 down vote accepted

Your question seems somewhat confused. WAFL is the name for a proprietary filesystem used in the products of the company NetApp. If you'd like to learn more about filesystem design or the importance of caching, that's great, but this isn't the right place to ask.

share|improve this answer
Where's the right Stack Exchange category? – Dark Templar Oct 14 '11 at 20:03

Not the answer you're looking for? Browse other questions tagged or ask your own question.