[reiserfs-list] RE: [OpenAFS-devel] weird issue with reiserfs on 2.4.3 and openaf s

[aeneous@speakeasy.org]

> 
> If all AFS cache files are in one directory, and files don't get moved into
> that directory from elsewhere in the FS (ie mv /tmp/foo /afs_cache_dir),
> than 
> the extra 32 bits of info reiserfs needs will always be the same as the
> inode number of the cache directory, and we can whip up something using
> iget4 to pass the extra info to reiserfs.

This is correct.  The cache files are only created and deleted by afsd, and should not ever be moved in from elsewhere.  afsd could verify that this is the case when it scans the cache at startup.