[OpenAFS-devel] RE: fsck

[Neulinger, Nathan R.]

What about the approach of the linux AFS server? It looks to me like it
creates files in the directories on the system corresponding to AFS files.
Why not just use this approach everywhere. It would certainly eliminate any
of the issues with porting and supporting the server.

-- Nathan

> -----Original Message-----
> From: Lyle Seaman [mailto:lws@spinnakernet.com]
> Sent: Monday, November 06, 2000 3:50 PM
> To: stan@fnal.gov
> Cc: info-afs@transarc.com
> Subject: Re: fsck
> 
> 
> stan@fnal.gov 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.
> 
> 
> 
>