[OpenAFS] Inode fileserver partitions "vicep(x)" on Veritas VxVM volumes OK ??

[chas williams - CONTRACTOR]

In message <816F4A58BB712010D07B6D32@[10.1.0.183]>,Joshua Johnson writes:
>Is this Correct ? -
>
>-- Using Inode fileserver partitions "/vicep(x)" on VxVM volumes is OK, do 
>not use VxFS, usual vfsck warnings apply.

yes, assuming the filesystem is ufs and ufslogging is disabled (its
enabled by default with the advent of solaris10).

>Is this Correct ? -
>
>-- To use VxFS, you MUST build and use an OpenAFS NAMEI fileserver instead, 
>which incurs a slight performance penalty (~10% compared to inode -- YMMV), 
>but you have a normal filesystem as underlying store.

yes -- the performance penalty is a bit of hot topic.  since you can
use ufslogging this should boost performance of file creation/deletion
which should help offset penalties there.  not having to fsck the
partition is a huge time saver after a hard failure.

>Any other large caveats (Veritas VxVM vs. OpenAFS 1.2.x & 1.3.x) ?

only 1.3.x has support for files >2G.  if you are going to have a huge
partition with lots of volumes, you might consider some of the
other options like --enable-fast-restart and --enable-bitmap-later.