my understanding is that knfsd wants to use inode numbers in the handles
that it passes out to clients (which must persis across server restarts).
and inode numbers are not unique across filesystems. what I don't know is
why it can't hash the inode with some per-FS id to accomplish the obviously
desirable behavior. is it that re-exporting the same file two ways
presents a permissions/accounting pain?
thanks, mark hahn.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/