On Sun, Mar 27, 2011 at 2:10 PM, Pavel Shilovsky <piastry@xxxxxxxxxxx> wrote: > 2011/3/27 Steve French <smfrench@xxxxxxxxx>: > As for fsycn logic - as I understand this call - it ought to > synchronize data between a cache and storage device. But if we can't > free pages, we don't successfully complete this synchronization - so, > reporting -EBUSY error here doesn't seem wrong to me (may be we should > set -EIO error code - according to the man page). If I am mistaken, > please, explain your points. To me synchronizing means that all data was written to the server that was dirty at the time of the call. When we try to free the page we have already flushed all data that was dirty at the time the fsync call began, but there is nothing that does or should prevent other processes from writing to that file. -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
