From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: lsf-pc@lists.linux-foundation.org
Cc: xfs <xfs@oss.sgi.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
ocfs2-devel@oss.oracle.com
Subject: [LFS/MM TOPIC] fs reflink issues, fs online scrub/check, etc
Date: Wed, 10 Feb 2016 11:18:48 -0800 [thread overview]
Message-ID: <20160210191848.GC6346@birch.djwong.org> (raw)
In-Reply-To: <20160210191715.GB6339@birch.djwong.org>
[resend, email exploded, sorry...]
Hi,
I want to discuss a few FS related topics that I haven't already seen on
the mailing lists:
* Shared pagecache pages for reflinked files (and by extension making dax
work with reflink on xfs)
* Providing a simple interface for scrubbing filesystem metadata in the
background (the online check thing). Ideally we'd make it easy to discover
what kind of metadata there is to check and provide a simple interface to
check the metadata, once discovered. This is a tricky interface topic
since FS design differs pretty widely.
* Rudimentary online repair and rebuilding (xfs) from secondary metadata
* Working out the variances in the btrfs/xfs/ocfs2/nfs reflink implementations
and making sure they all get test coverage
I would also like participate in some of the proposed discussions:
* The ext4 summit (and whatever meeting of XFS devs may happen)
* Integrating existing filesystems into pmem, or hallway bofs about designing
new filesystems for pmem
* Actually seeing the fs developers (well, everyone!) in person again :)
--Darrick
next parent reply other threads:[~2016-02-10 19:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160210191715.GB6339@birch.djwong.org>
2016-02-10 19:18 ` Darrick J. Wong [this message]
2020-01-21 0:58 ` [LFS/MM TOPIC] fs reflink issues, fs online scrub/check, etc Steve French
2020-01-21 1:18 ` Qu Wenruo
2020-01-21 7:35 ` [Lsf-pc] " Amir Goldstein
2020-01-21 16:18 ` Darrick J. Wong
2020-01-21 22:01 ` Matthew Wilcox
2020-01-22 0:47 ` Dan Williams
2020-01-22 8:21 ` Dave Chinner
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=20160210191848.GC6346@birch.djwong.org \
--to=darrick.wong@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ocfs2-devel@oss.oracle.com \
--cc=xfs@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).