Re: [PATCH v2 0/4] vfs: track per-sb writeback errors and report them via fsinfo()

On Tue, Jul 10, 2018 at 10:01:23AM -0400, Jeff Layton wrote: > v2: drop buffer.c patch to record wb errors when underlying blockdev > flush fails. We may eventually want that, but at this point I don't have > a clear way to test it to determine its efficacy. > > At LSF/MM this year, the PostgreSQL

Re: [PATCH v2 0/4] vfs: track per-sb writeback errors and report them via fsinfo()

Jeff Layton wrote: > v2: drop buffer.c patch to record wb errors when underlying blockdev > flush fails. We may eventually want that, but at this point I don't have > a clear way to test it to determine its efficacy. > > At LSF/MM this year, the PostgreSQL developers mentioned that they'd > like

[PATCH v2 0/4] vfs: track per-sb writeback errors and report them via fsinfo()

v2: drop buffer.c patch to record wb errors when underlying blockdev flush fails. We may eventually want that, but at this point I don't have a clear way to test it to determine its efficacy. At LSF/MM this year, the PostgreSQL developers mentioned that they'd like to have some mechanism to check