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

[Derek Atkins]

Ok, how about this..  Let's assume that in user-mode we bring the file
into the inode cache and then pass just the inode number down to the
kernel.  In the kernel, is there some (easy) way to notice that we're
using reiserfs?  If so, perhaps when we initiate the cache file we can
check if it's reiserfs and, if so, open the inode (which is currently
in the cache), grab the extra data, save the extra data (somewhere),
and then release it.  Then, later, we can check the saved data and
notice that the file was reiserfs and behave specially.

I really don't like this solution.. It's a complete kludge and
special-case for reiserfs..  But I think it would solve our problem
until, as you say, we move to 64-bit inodes :)

-derek

Chris Mason <mason@suse.com> writes:

> Grin, we could spend many hours debating this, but the simple truth is that
> even if I agreed with you (which I do), the reiserfs disk format isn't
> going to change.  reiserfs inode number are unique, but not enough to find
> the file.  If/when the kernel switches to 64 bit inode numbers, we'll be
> ready.
> 
> Until then, I'd like to find a way to make reiserfs+AFS play nice.  This
> either means keeping the inodes pinned (ick), or finding a way to have AFS
> sends us the extra 32 bits.  I'm more than willing to help out with that,
> we just need somewhere in AFS to store the 32 bits.
> 
> -chris
> 
> 

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord@MIT.EDU                        PGP key available