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

[Neulinger, Nathan]

> -----Original Message-----
> From: Chris Mason [mailto:mason@suse.com]
> Sent: Wednesday, April 11, 2001 3:01 PM
> To: Neulinger, Nathan; 'Danilov Nikita'
> Cc: 'reiserfs-list@namesys.com'; 'openafs-devel@openafs.org'
> Subject: RE: [reiserfs-list] RE: [OpenAFS-devel] weird issue with
> reiserfs on 2.4.3 and openaf s
> 
> 
> 
> 
> On Wednesday, April 11, 2001 01:25:23 PM -0500 "Neulinger, Nathan"
> <nneul@umr.edu> wrote:
> 
> > Actually, in the ideal case of an AFS cache being on it's 
> own filesystem,
> > there should only be 1 directory on the whole filesystem (and maybe
> > lost+found), which is why it ran fine on 3.5.
> > 
> 
> 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.
> 
> Otherwise, we'll have to do something else (more details in 
> another email).

The above presumptions are correct (unless user is doing something weird, in
which case, who cares).

-- Nathan