I don't think there's a way to have that information.
The reason is, that the filesystem does not necessarily support that notion. Typically, how would a NFS drive work with that ? It would need to redirect the calls to the remote server.

A problem can be, that the physical drive has internal caches that are NOT flushed on request, and therefore data is still NOT actually written after the OS made the flush request.
In other cases, one drive is replicated into 2 others, with them being used as check, so if the data is written in the first one but not yet in the replicate, then the data is not actually stored.

This notion is the base of the "durability" issue in databases. That's why DB system are so difficult to manage, and some system show huge performance gain … simply because they ignore it.

More info : https://en.wikipedia.org/wiki/Durability_(database_systems)