From: Martin Steigerwald <martin@lichtvoll.de>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [RFD] XFS: Subvolumes and snapshots....
Date: Sun, 28 Jan 2018 13:59:56 +0100 [thread overview]
Message-ID: <10612480.yRmMisqFVa@merkaba> (raw)
In-Reply-To: <20180125055144.qztiqeakw4u3pvqf@destitution>
Dave Chinner - 25.01.18, 06:51:
> The video from my talk at LCA 2018 yesterday about the XFS subvolume and
> snapshot support I'm working on has been uploaded and can be found
> here:
>
> https://www.youtube.com/watch?v=wG8FUvSGROw
I somehow knew that something about snapshots would be coming for XFS after
seeing the reflink / COW and online scrub/repair work by Darrick. But I am
highly surprised on the how. I also did not really expect pNFS file layout of
Christoph to play a role here.
It totally makes sense to me right now, but on the other hand I found myself
thinking "It can´t be that easy, can it?" after watching your talk.
Easy not in amount of coding work needed and some complexities you mentioned,
so I totally get that it is a lot of work needed to pull this off, but easy in
terms of the concept behind it. Yet, if a concept is easy that is quite a hint
that it might actually be a good one. And if you really can get away with it…
then by all means, have a go at it!
I am looking forward to this new "extraordinary way to eat your data"
(Darrick) or create "blammo" and "kaboom" (Dave). :)
>From what I understand it is also way less of a "layering violation" than the
approach in taken in BTRFS or ZFS. Actually it might not be a "layering
violation" at all, since the different layers are still there and
communicating with each other. Which opens a lot of potential on applying this
to other filesystems and storage subsystems of the kernel.
I see benefit in having more than one concept and learn from each other. Maybe
even a new dog like BTRFS can learn a trick from an old dog at some point in
time. It sounds crazy to me to think like this at the moment… but for a long
time it sounded crazy to try to implement snapshots or subvolumes to
traditional filesystems.
Kudos to thinking out of the box!
--
Martin
next prev parent reply other threads:[~2018-01-28 13:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 5:51 [RFD] XFS: Subvolumes and snapshots Dave Chinner
2018-01-27 8:34 ` Amir Goldstein
2018-01-27 11:28 ` Dave Chinner
2018-01-27 15:56 ` Amir Goldstein
2018-01-28 1:57 ` Dave Chinner
2018-01-27 17:05 ` Martin Raiber
2018-01-28 1:59 ` Dave Chinner
2018-01-28 12:59 ` Martin Steigerwald [this message]
2018-01-29 1:50 ` Dave Chinner
2021-08-23 4:57 ` Chris Dunlop
2021-08-23 23:12 ` 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=10612480.yRmMisqFVa@merkaba \
--to=martin@lichtvoll.de \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).