public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	xfs <linux-xfs@vger.kernel.org>,
	linux-ext4 <linux-ext4@vger.kernel.org>,
	linux-btrfs <linux-btrfs@vger.kernel.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [Lsf-pc] [LSF TOPIC] online repair of filesystems: what next?
Date: Tue, 18 Apr 2023 19:11:46 -0700	[thread overview]
Message-ID: <20230419021146.GE360889@frogsfrogsfrogs> (raw)
In-Reply-To: <CAOQ4uxgUOuR80jsAE2DkZhMPVNT_WwnsSX8-GSkZO4=k3VbCsw@mail.gmail.com>

On Tue, Apr 18, 2023 at 10:46:32AM +0300, Amir Goldstein wrote:
> On Tue, Apr 18, 2023 at 7:46 AM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > On Sat, Apr 15, 2023 at 03:18:05PM +0300, Amir Goldstein wrote:
> > > On Tue, Feb 28, 2023 at 10:49 PM Darrick J. Wong <djwong@kernel.org> wrote:
> ...
> > > Darrick,
> > >
> > > Quick question.
> > > You indicated that you would like to discuss the topics:
> > > Atomic file contents exchange
> > > Atomic directio writes
> >
> > This one ^^^^^^^^ topic should still get its own session, ideally with
> > Martin Petersen and John Garry running it.  A few cloud vendors'
> > software defined storage stacks can support multi-lba atomic writes, and
> > some database software could take advantage of that to reduce nested WAL
> > overhead.
> >
> 
> CC Martin.
> If you want to lead this session, please schedule it.
> 
> > > Are those intended to be in a separate session from online fsck?
> > > Both in the same session?
> > >
> > > I know you posted patches for FIEXCHANGE_RANGE [1],
> > > but they were hiding inside a huge DELUGE and people
> > > were on New Years holidays, so nobody commented.
> >
> > After 3 years of sparse review comments, I decided to withdraw
> > FIEXCHANGE_RANGE from general consideration after realizing that very
> > few filesystems actually have the infrastructure to support atomic file
> > contents exchange, hence there's little to be gained from undertaking
> > fsdevel bikeshedding.
> >
> > > Perhaps you should consider posting an uptodate
> > > topic suggestion to let people have an opportunity to
> > > start a discussion before LSFMM.
> >
> > TBH, most of my fs complaints these days are managerial problems (Are we
> > spending too much time on LTS?  How on earth do we prioritize projects
> > with all these drive by bots??  Why can't we support large engineering
> > efforts better???) than technical.
> 
> I penciled one session for "FS stable backporting (and other LTS woes)".
> I made it a cross FS/IO session so we can have this session in the big room
> and you are welcome to pull this discussion to any direction you want.

Ok, thank you.  Hopefully we can get all the folks who do backports into
this one.  That might be a big ask for Chandan, depending on when you
schedule it.

(Unless it's schedule for 7pm :P)

> >
> > (I /am/ willing to have a "Online fs metadata reconstruction: How does
> > it work, and can I have some of what you're smoking?" BOF tho)
> >
> 
> I penciled a session for this one already.
> Maybe it would be interesting for the crowd to hear some about
> "behind the scenes" - how hard it was and still is to pull off an
> engineering project of this scale - lessons learned, things that
> you might have done differently.

Thanks!

--D

> 
> Cheers,
> Amir.

  reply	other threads:[~2023-04-19  2:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 20:49 [LSF TOPIC] online repair of filesystems: what next? Darrick J. Wong
2023-03-08 17:12 ` Jan Kara
2023-03-08 21:54   ` Dave Chinner
2023-03-09 16:00     ` Darrick J. Wong
2023-03-09 18:26       ` Ritesh Harjani
2023-03-14  2:14         ` Darrick J. Wong
2023-03-15  3:45           ` Ritesh Harjani
2023-03-09 17:49     ` Jan Kara
2023-04-15 12:18 ` [Lsf-pc] " Amir Goldstein
2023-04-18  4:46   ` Darrick J. Wong
2023-04-18  7:46     ` Amir Goldstein
2023-04-19  2:11       ` Darrick J. Wong [this message]
2023-04-19  4:06         ` Amir Goldstein
2023-04-19 10:58           ` Chandan Babu R
2023-04-20  4:32             ` Darrick J. Wong
2023-04-20  4:47               ` Chandan Babu R
2023-04-19  3:34       ` Matthew Wilcox
2023-04-19  4:02         ` Amir Goldstein
2023-04-16  8:10 ` Qu Wenruo
2023-04-16  8:43   ` [Lsf-pc] " Amir Goldstein

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=20230419021146.GE360889@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=martin.petersen@oracle.com \
    /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