journald fsync() errors

[vcaputo@xxxxxxxxxxx (vcaputo@xxxxxxxxxxx)]

Back when I worked on making fsync() in journald asynchronous, I
preserved the existing strategy of ignoring fsync() errors.

In reading [1], I am reminded of this situation and am again wondering
why this is the case.  Shouldn't journald trigger a journal rotate when
fsync() realizes an IO error, marking the previous journal as corrupt?

Can someone remind me of the rationale behind the existing approach?

Regards,
Vito Caputo

[1] https://www.postgresql.org/message-id/flat/CAMsr%2BYE5Gs9iPqw2mQ6OHt1aC5Qk5EuBFCyG%2BvzHun1EqMxyQg%40mail.gmail.com