On Wed, Apr 04, 2018 at 04:49:29PM +0200, Lennart Poettering wrote:
> On Di, 03.04.18 14:10, vcap...@pengaru.com (vcap...@pengaru.com) wrote:
>
> > Back when I worked on making fsync() in journald asynchronous, I
> > preserved the existing strategy of ignoring fsync() errors.
> >
> > In reading [
On Di, 03.04.18 14:10, vcap...@pengaru.com (vcap...@pengaru.com) wrote:
> 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 cas
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,
