From: RayLink Date: Thu, 4 Mar 2004 14:57:40 +0000 (+0000) Subject: none X-Git-Url: https://git.openafs.org/?p=openafs-wiki.git;a=commitdiff_plain;h=1024dacdf02e669bb69a3fd94b152d417fb6826f;hp=8b7590d09e92b21512893310ad3a745d56f93016 none --- diff --git a/AFSLore/ReiserFS.mdwn b/AFSLore/ReiserFS.mdwn new file mode 100644 index 0000000..6adac49 --- /dev/null +++ b/AFSLore/ReiserFS.mdwn @@ -0,0 +1,25 @@ +## Where can you use [[ReiserFS]]? + +There seems to be much confusion amongst new [[OpenAFS]] administrators about when and where they can use [[ReiserFS]]. This document attempts to describe supported uses, and explain why the others are unsupported. + +---- + +### Supported: Vice partitions on namei-based fileservers + +**Why:** Namei-based fileservers store volumes in regular files on the vice partitions. No meta-data is stored in the inodes of these files. + +---- + +### Unsupported: Vice partitions on inode-based fileservers + +**Why:** Inode-based fileservers access volumes directly via inode, and sneakily stuff bits of volume metadata into portions of the inode structure. Since [[ReiserFS]] does not have persistent inodes, this process will not work. + +---- + +### Unsupported: Cache partitions on [[OpenAFS]] clients + +**Why:** The cache manager operates directly on filesystem inodes. [[ReiserFS]] does not have persistent inodes. + +---- + +-- [[RayLink]] - 04 Mar 2004 diff --git a/AFSLore/SupportedConfigurations.mdwn b/AFSLore/SupportedConfigurations.mdwn index a0e5692..fc62e22 100644 --- a/AFSLore/SupportedConfigurations.mdwn +++ b/AFSLore/SupportedConfigurations.mdwn @@ -81,7 +81,7 @@ You can easily see that you are using an NAMEI file server if there is a directo These Don't Work - reiserfs, vxfs (HP-UX, Solaris), AdvFS (OSF1/DigitalUnix/CompaqUnix/Tru64Unix) + [[Main/ReiserFS]], vxfs (HP-UX, Solaris), AdvFS (OSF1/DigitalUnix/CompaqUnix/Tru64Unix)