[EMAIL PROTECTED] wrote:
> In the OpenAFS announcement it was made mention that fsck is not available.
> How will that impact OpenAFS for servers other that Digital which we don't use.
It won't affect the cache manager or database servers.
Since afs inodes aren't connected to the native directories, the native fsck
believes
that they are "orphaned" and sticks them all in lost+found. A second pass will
delete
them. This design decision has probably caused more grief than any other.
The Episode file system project (the DCE/DFS local file system) was supposed to
put this right, but that's a different story.
I would recommend against trying to retrofit the fsck functionality in the OpenAFS
environment, in favor of some alternative approach. ISTR that zumach's work on
the
SGI XFS port did this "right"; take a look at that.
