On 2019-05-22 14:46, Cerem Cem ASLAN wrote:
Could you confirm or disclaim the following explanation:
https://unix.stackexchange.com/a/520063/65781
Aside from what Hugo mentioned (which is correct), it's worth mentioning
that the example listed in the answer of how hardware issues could screw
things up assumes that for some reason write barriers aren't honored.
BTRFS explicitly requests write barriers to prevent that type of
reordering of writes from happening, and it's actually pretty unusual on
modern hardware for those write barriers to not be honored unless the
user is doing something stupid (like mounting with 'nobarrier' or using
LVM with write barrier support disabled).
