On Sun, Sep 29, 2013 at 11:22:36AM +0200, Aastha Mehta wrote: > Thank you very much for the reply. That clarifies a lot of things. > > I was trying a small test case that opens a file, writes a block of > data, calls fsync and then closes the file. If I understand correctly, > fsync would return only after all in-memory buffers have been > committed to disk. I have added few print statements in the > __extent_writepage function, and I notice that the function gets > called a bit later after fsync returns. It seems that I am not > guaranteed to see the data going to disk by the time fsync returns. > > Am I doing something wrong, or am I looking at the wrong place for > disk write? This happens both with tree logging enabled as well as > with notreelog. >
So 3.1 was a long time ago and to be sure it had issues I don't think it was _that_ broken. You are probably better off instrumenting a recent kernel, 3.11 or just build btrfs-next from git. But if I were to make a guess I'd say that __extent_writepage was how both data and metadata was written out at the time (I don't think I changed it until 3.2 or something later) so what you are likely seeing is the normal transaction commit after the fsync. In the case of notreelog we are likely starting another transaction and you are seeing that commit (at the time the transaction kthread would start a transaction even if none had been started yet.) Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
