From: Seth Forshee <seth.forshee@canonical.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
containers@lists.linux-foundation.org,
linux-fsdevel@vger.kernel.org
Cc: "Stéphane Graber" <stgraber@ubuntu.com>,
"Christian Brauner" <christian.brauner@canonical.com>,
"Tyler Hicks" <tyler.hicks@canonical.com>
Subject: shiftfs status and future development
Date: Thu, 14 Jun 2018 13:44:48 -0500 [thread overview]
Message-ID: <20180614184448.GC30028@ubuntu-xps13> (raw)
I wanted to inquire about the current status of shiftfs and the plans
for it moving forward. We'd like to have this functionality available
for use in lxd, and I'm interesetd in helping with development (or
picking up development if it's stalled).
To start, is anyone still working on shiftfs or similar functionality? I
haven't found it in any git tree on kernel.org, and as far as mailing
list activity the last submission I can find is [1]. Is there anything
newer than this?
Based on past mailing list discussions, it seems like there was still
debate as to whether this feature should be an overlay filesystem or
something supported at the vfs level. Was this ever resolved?
Thanks,
Seth
[1] http://lkml.kernel.org/r/1487638025.2337.49.camel@HansenPartnership.com
next reply other threads:[~2018-06-14 18:44 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 18:44 Seth Forshee [this message]
2018-06-15 13:56 ` shiftfs status and future development Serge E. Hallyn
2018-06-15 14:59 ` Seth Forshee
2018-06-15 15:25 ` Matthew Wilcox
2018-06-15 15:56 ` Aleksa Sarai
2018-06-15 16:09 ` James Bottomley
2018-06-15 17:04 ` Aleksa Sarai
2018-06-15 17:22 ` James Bottomley
2018-06-15 20:47 ` Seth Forshee
2018-06-15 21:09 ` James Bottomley
2018-06-15 21:35 ` Seth Forshee
2018-06-16 3:03 ` James Bottomley
2018-06-18 13:40 ` Seth Forshee
2018-06-18 13:49 ` Amir Goldstein
2018-06-18 14:56 ` James Bottomley
2018-06-18 16:03 ` Seth Forshee
2018-06-18 17:11 ` Amir Goldstein
2018-06-18 19:53 ` Phil Estes
2018-06-21 20:16 ` Seth Forshee
2018-06-24 11:32 ` Amir Goldstein
2018-06-25 11:19 ` Christian Brauner
2018-06-27 7:48 ` James Bottomley
2018-06-27 10:17 ` Amir Goldstein
2018-07-03 16:54 ` Serge E. Hallyn
2018-07-03 17:08 ` Stéphane Graber
2018-07-03 22:05 ` Serge E. Hallyn
2018-06-15 14:54 ` Aleksa Sarai
2018-06-15 15:05 ` Seth Forshee
2018-06-15 15:28 ` James Bottomley
2018-06-15 15:46 ` Seth Forshee
2018-06-15 16:16 ` Christian Brauner
2018-06-15 16:35 ` James Bottomley
2018-06-15 20:17 ` Seth Forshee
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=20180614184448.GC30028@ubuntu-xps13 \
--to=seth.forshee@canonical.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=christian.brauner@canonical.com \
--cc=containers@lists.linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=stgraber@ubuntu.com \
--cc=tyler.hicks@canonical.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).