From d73cb612b5ed7c51ee459fb859fca1e1d520ee27 Mon Sep 17 00:00:00 2001
From: Chris Lu <chris.lu@gmail.com>
Date: Sun, 17 Jun 2018 17:36:28 -0700
Subject: [PATCH] remove verbose explanation

---
 Directories-and-Files.md | 11 -----------
 1 file changed, 11 deletions(-)

diff --git a/Directories-and-Files.md b/Directories-and-Files.md
index 601ed92..1b755aa 100644
--- a/Directories-and-Files.md
+++ b/Directories-and-Files.md
@@ -43,17 +43,6 @@ visit "http://localhost:8888/path/to/sources/"
 visit "http://localhost:8888/path/to/sources/?lastFileName=abc.txt&limit=50"
 ```
 
-### Design
-
-A common file system would use inode to store meta data for each folder and file. The folder tree structure are usually linked. And sub folders and files are usually organized as an on-disk b+tree or similar variations. This scales well in terms of storage, but not well for fast file retrieval due to multiple disk access just for the file meta data, before even trying to get the file content.
-
-SeaweedFS wants to make as small number of disk access as possible, yet still be able to store a lot of file metadata. So we need to think very differently.
-
-We can take the following steps to map a full file path to the actual data block:
-
-1. map <file_parent_directory, fileName> to <attributes, a list of file_id> Implemented by "weed filer" server.
-2. map <file_id> to <data_blocks>. Implemented by default SeaweedFS master and volume servers.
-
 #### Architecture
 
 For file reads: