[lkml]   [1997]   [Nov]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: knfsd and system crashes
    > I've currently got the third-level (when we have a parent dentry) search
    > working, but I'm a little unclear on the best strategy for implementing
    > the full volume search given device number and parent inode/inode
    > number. Can you offer some suggestions here?

    PMFJI, I think the problem is the assumption that the volume has to
    be searched in the first place. Most file systems can open an inode
    very efficiently when given an inode number.

    The Linux VFS currently offers the iget function to retrieve an inode
    when given an inode number. Unfortunately, this interface is not very
    reliable when it comes to error checking, like when the client gives a
    stale handle. Nevertheless, this is IMHO the route to go. You can
    either extend the read_inode operation to support better error
    reporting for deleted inodes, or introduce new interface.

    Searching the entire volume is not an option, IMHO - at least not on
    file systems that have the clear notion of inode numbers.


     \ /
      Last update: 2005-03-22 13:40    [W:0.018 / U:28.456 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site