From: Iustin Pop <iustin@k1024.org>
To: linux-xfs@vger.kernel.org
Subject: reflink status?
Date: Tue, 18 Dec 2018 22:22:07 +0100 [thread overview]
Message-ID: <20181218212207.GA27985@teal.hq.k1024.org> (raw)
Apologies if this information is available somewhere, but a quick scan
at the list archives failed to clarify things for me.
How production ready is the reflink/clone code? I saw a patch series in
October for 4.19rc-something with many fixes ("fixes for serious
clone/dedupe problems"), so I guess pre-4.19 kernels are not quite
recommended yet? Is 4.19 OK for it?
Thanks in advance for any hints. Pointers to where I can keep up to date
with this besides the mailing list are also welcome.
regards,
iustin
next reply other threads:[~2018-12-18 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 21:22 Iustin Pop [this message]
2018-12-19 5:30 ` reflink status? Dave Chinner
2018-12-19 21:30 ` Iustin Pop
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=20181218212207.GA27985@teal.hq.k1024.org \
--to=iustin@k1024.org \
--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