ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Project Banbury
Date: Sun, 16 Sep 2018 19:03:40 +0300	[thread overview]
Message-ID: <2499181.JFuLfGgBK5@avalon> (raw)
In-Reply-To: <CAFhKne8kiF6k-QUJ9x-cCyBcVvfuWKdcUtQZNz=1sx_iHR+64g@mail.gmail.com>

Hi Matthew,

On Friday, 14 September 2018 20:28:01 EEST Matthew Wilcox wrote:
> We've all pulled the wrong drive out of a machine or unplugged a USB key
> before the write back has completely finished. You try to plug it back in,
> but the damage is done. The pending writes are lost, the filesystem is
> damaged and full of errors and you are having a Bad Day. What if ...
> plugging the drive back in could be made to work?
> 
> This session would be more of a discussion than a presentation since I've
> not written a single line of code towards fixing the problem. I have
> written a web page sketching out an architecture for how we might make this
> work:
> 
> http://www.wil.cx/~willy/banbury.html

Having lost a server due to a DDoS attach that rendered the link between CPU 
and storage unusable for a too long time, I think this would be an amazing 
improvement.

-- 
Regards,

Laurent Pinchart

  parent reply	other threads:[~2018-09-16 16:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-14 17:28 Matthew Wilcox
2018-09-16 10:53 ` Hannes Reinecke
2018-09-16 12:45   ` Matthew Wilcox
2018-09-18  8:17     ` Hannes Reinecke
2018-09-16 16:03 ` Laurent Pinchart [this message]
2018-09-16 16:25   ` Linus Torvalds
2018-09-16 16:37 ` James Bottomley
2018-09-16 19:25   ` Theodore Y. Ts'o
2018-09-16 23:58 ` David Howells

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=2499181.JFuLfGgBK5@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox