Subject: Re: andrew FS client?
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>
From: Bill Sommerfeld <sommerfeld@orchard.medford.ma.us>
List: current-users
Date: 11/21/1995 22:03:53
-----BEGIN PGP SIGNED MESSAGE-----

> From looking at things, what everyone is primarily interested in is the
> struct dinode, right?  (Since that's what lives on disk).

Right.

> A lot of other AFS ports seem to use di_gen (or similar) for vicemagic.  A
> quick grep through the ufs tree doesn't show that it's being used; looks
> like it's okay.

di_gen should be used as the NFS "generation number", incremented each
time an inode gets recycled..  It's been a while since I looked at the
fileserver in detail, but I believe that one of the *other* vicep?
fields is used in exactly the same way.

> ... but let's pretend we're not going to run LFS underneath AFS.

Why not? (well, other than the fact that there isn't an fsck for LFS
yet....).. after all, AFS access patterns (whole file/large chunk
read/write) should fit real well with LFS..

> So, does this make sense?  Or did I miss something?

Well, the approach taken by AFS ports on systems which don't have
sufficient slush fields in the inode is to stuff the additional fields
into a separate file indexed by the inode number; that's probably
safer, albeit slower..

					- Bill

-----BEGIN PGP SIGNATURE-----
Version: 2.6.1

iQCVAwUBMLKTFrT+rHlVUGpxAQHygwP9EOaCx8mSds05yAf9eEe65gbBLC/ivGJk
9TfMCtwgKNU8CGPDzeD15gehJn4pg/GD+et8sFoeWPXa+yOoUabq82CRSDKW6doN
Olnk9ySTZchSEH9MYmyAe4qMXfeHOofdhThaGeFsng1mfy31P9KAIynZ/afBOcHY
uYpmE5YfbBE=
=bOSc
-----END PGP SIGNATURE-----