From: Trond Myklebust <trondmy@hammer.space>
To: "andres@anarazel.de" <andres@anarazel.de>,
"willy@infradead.org" <willy@infradead.org>
Cc: "david@fromorbit.com" <david@fromorbit.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] improving writeback error handling
Date: Thu, 19 Apr 2018 02:19:16 +0000 [thread overview]
Message-ID: <1524104354.38378.24.camel@hammer.space> (raw)
In-Reply-To: <20180419021548.sxx7ormrkvnrseys@alap3.anarazel.de>
On Wed, 2018-04-18 at 19:15 -0700, andres@anarazel.de wrote:
> On 2018-04-18 18:57:23 -0700, Matthew Wilcox wrote:
> > 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..
>
> Correct. Do you want a summary here or at LSF/MM? Thanks to Jon
> Corbet
> I've got a last minute invitation.
>
I'm not attending LSF/MM this year.
Cheers
Trond
next prev parent reply other threads:[~2018-04-19 2:19 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
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 [this message]
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=1524104354.38378.24.camel@hammer.space \
--to=trondmy@hammer.space \
--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=willy@infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.