"NASA/AMES is asking for the ability to be able to tell users which files may be suspect after an
adverse cluster event; panics, hangs, client evictions, etc.

One example that may be easier than others is when a client is evicted and the client is forced to
toss dirty pages of open files. The site has been experimenting with a way to list the inode
numbers on the mds with the associated pages tossed on the clients. I'll leave it to them to
discuss here.
" – from Oracle BZ 21812.

Oracle has released a patch (attachment 33114.) It affected client side. We like Whamcloud to include this patch for 1.8.x and 2.1.x.