commit 2e5a1f4e8f3eed79347cb2ecd3c4c06ea9c03d46
Author: Yiannis Pericleous <[EMAIL PROTECTED]>
Date: Wed Mar 28 16:55:22 2007 -0400
documentation: updated usage.txt and added odf.txt
diff --git a/Documentation/filesystems/unionfs/odf.txt
b/Documentation/filesystems/unionfs/odf.txt
index bb3b751..5556006 100644
--- a/Documentation/filesystems/unionfs/odf.txt
+++ b/Documentation/filesystems/unionfs/odf.txt
@@ -170,9 +170,9 @@ normal user's view.
An /odf is a hierarchy of directories and files with specific purposes, as
follows:
-1. /odf/sb contains the whiteoute file and a file containing our superblock,
- which records branch configuration, UUIDs, etc. Each branch has a unique
- UUID so it can be identified consistently.
+1. /odf/sb is a plain file containing our superblock, which records branch
+ configuration, UUIDs, etc. Each branch has a unique UUID so it can be
+ identified consistently.
2. /odf/ns/<PATH> is used for storing information about whiteouts, opaque
directories, and persistent inode numbers. We use the actual inum of the
@@ -240,6 +240,10 @@ The ODF superblock (/odf/sb) stores the following:
options again. (Optional: we can record portable information such as a
file system's LABEL.)
+- records whether this odf is newly formatted or in use. (We can store a
+ "new" bit which is initialized on mkfs, or just count the number of inodes
+ in use.)
+
- we might also need to record extra info to handle hardlinks (e.g., the
orig branch pathname from root of that branch's file system up to the
lower-branch dir name we stack on)
_______________________________________________
unionfs-cvs mailing list: http://unionfs.filesystems.org/
[email protected]
http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs-cvs
