1 ## <a name="NAMEI vs. inode based file serve"></a> NAMEI vs. inode based file server
3 There are two different flavours of the AFS file server (the fs process): One uses inodes to store AFS data (volumes, files, metadata), the other uses real files.
5 The inode-based server needs a file system which supports access by inode and usually a special fsck is required so that the AFS data is not corrupted (since the server does some behind-the-scenes stuff with the file system). The NAMEI file server does not pose any unusual constraints on the underlying filesystem - it's an ordinary userspace program working with (silly-named) files.
7 You can easily see that you are using an NAMEI file server if there is a directory named `AFSIDat` and with subdirectories like `+` and `+1` in your `/vicep*`.
9 -- Tino Schwarze - 25 Jul 2003
11 ## <a name="Recommended Partition Types for"></a><a name="Recommended Partition Types for "></a> Recommended Partition Types for use with [[OpenAFS]]
13 <table border="1" cellpadding="0" cellspacing="0">
15 <th bgcolor="#99CCCC"><strong> namei Server </strong></th>
16 <th bgcolor="#99CCCC"><strong> Server vicexx Partition Types </strong></th>
19 <td> Any system type </td>
20 <td> Basically any filesystem you like, as the new namei file server does not do any fancy stuff behind the scenes but only accesses normal files (their names are a bit strange though). </td>
24 <table border="1" cellpadding="0" cellspacing="0">
26 <th bgcolor="#99CCCC"><strong> inode Server </strong></th>
27 <th bgcolor="#99CCCC"><strong> Server vicexx Partition Types </strong></th>
30 <td> sun4x_5[789] </td>
31 <td><code>ufs</code> w/o logging </td>
34 <td> aix_4[345] , aix_51 </td>
35 <td><code>jfs</code></td>
39 <td><code>XFS</code></td>
42 <td> ppc_darwin_14 </td>
46 <td> alpha_dux[40,50,51] </td>
47 <td><code>ufs</code> , no <code>AdvFS</code> support </td>
51 <table border="1" cellpadding="0" cellspacing="0">
53 <th bgcolor="#99CCCC"><strong> Client </strong></th>
54 <th bgcolor="#99CCCC"><strong> Cache (<code>/usr/vice/cache</code>)Partition Types </strong></th>
57 <td> i386_linux24 </td>
58 <td><code>ext2</code>, <code>ext3</code></td>
61 <td> sun4x_5[789] </td>
62 <td><code>ufs</code> without logging or dedicated ufs cache partition with logging, <code>vxfs</code></td>
65 <td> aix_4[345] , aix_51 </td>
66 <td><code>jfs</code></td>
70 <td><code>XFS</code></td>
73 <td> ppc_darwin_14 </td>
77 <td> These Don't Work </td>
78 <td>[[ReiserFS]], <code>vxfs</code> (HP-UX, Solaris), <code>AdvFS</code> (OSF1/DigitalUnix/CompaqUnix/Tru64Unix) </td>
82 Further, [[Tru64Unix]] 5.1 has only server support on ufs. The client is supported under Arla including `AdvFS` (but no server support as of Apr 2002). Server and client should work under DU4.0 and [[Tru64Unix]] 5.0.
84 - **Question:** Does this table imply that clients can't use the NAMEI backend and still need a specific filesystem? Will this ever change?
86 -- Todd Lewis - 06 Nov 2002
88 - **Another Question:** Does this mean that you can use an NFS mount point as a /vicexx if you use a NAMEI fileserver?
90 -- Chris McClimans - 25 Jul 2003