From: Matthew Wilcox <willy@infradead.org>
To: Trond Myklebust <trondmy@hammer.space>
Cc: "david@fromorbit.com" <david@fromorbit.com>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"andres@anarazel.de" <andres@anarazel.de>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] improving writeback error handling
Date: Wed, 18 Apr 2018 18:57:23 -0700 [thread overview]
Message-ID: <20180419015723.GC16782@bombadil.infradead.org> (raw)
In-Reply-To: <1524102468.38378.12.camel@hammer.space>
On Thu, Apr 19, 2018 at 01:47:49AM +0000, Trond Myklebust wrote:
> If the main use case is something like Postgresql, where you care about
> just one or two critical files, rather than monitoring the entire
> filesystem could we perhaps use a dedicated mmap() mode? It should be
> possible to throw up a bitmap that displays the exact blocks or pages
> that are affected, once the file has been damaged.
Perhaps we need to have a quick summary of the postgres problem ...
they're not concerned with "one or two files", otherwise they could
just keep those files open and the wb_err mechanism would work fine.
The problem is that they have too many files to keep open in their
checkpointer process, and when they come along and open the files,
they don't see the error..
next prev parent reply other threads:[~2018-04-19 1:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 11:08 [LSF/MM TOPIC] improving writeback error handling Jeff Layton
2018-04-17 22:53 ` Dave Chinner
2018-04-18 16:00 ` [Lsf-pc] " Jeff Layton
2018-04-19 0:44 ` Dave Chinner
2018-04-19 1:47 ` Trond Myklebust
2018-04-19 1:57 ` Matthew Wilcox [this message]
2018-04-19 2:12 ` Trond Myklebust
2018-04-19 18:57 ` andres
2018-04-19 2:15 ` andres
2018-04-19 2:19 ` Trond Myklebust
2018-04-19 17:14 ` Jeff Layton
2018-04-19 23:47 ` Dave Chinner
2018-04-20 11:24 ` Jeff Layton
2018-04-21 17:21 ` Jan Kara
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180419015723.GC16782@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=andres@anarazel.de \
--cc=david@fromorbit.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=trondmy@hammer.space \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).