Actually all the file systems who do that on Linux (JFS, XFS,
reiserfs) have fixed the issue properly server side, by adding a
layer that generates stable cookies. You should too.
I've always thought that was a stupid fix. Why not have the clients be
smarted and make them responsible for getting a new cookie if the old
one is hosed?
For linux, with the dcache, I'm not even sure that this would be all
the hard. Persumable Solaris could (does?) do the same?
--cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/