Correct, fsync is unchanged, but sync() does rely on the super dirty bit.
If the super isn't dirty, then sync doesn't try to force metadata to disk
at all.
>
> Sorry, I didn't grok that when writing my previous mail in this thread.
> I thought kupdate was the one that writes ReiserFS transactions, but
> that's kreiserfsd, I think.
Well, kreiserfsd usually writes the log blocks, when a transaction ends on
its own (full, or too old). If someone requests a synchronous commit
(fsync, any caller of write_super), that process writes the log blocks
themselves. So, kupdated ends up writing log blocks too.
Plus, reiserfs uses write_super as a trigger for metadata writeback, so
kupdate writes those blocks as well.
-chris
-
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/