public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 <velocifyer@velocifyer.com>
To: linux-btrfs@vger.kernel.org
Subject: Why does defragmenting break reflinks?
Date: Thu, 29 May 2025 19:52:31 -0400	[thread overview]
Message-ID: <9d74d71f-b65d-4f06-adb3-18f7698edb8a@velocifyer.com> (raw)

BTRFS-FILESYSTEM(8) says "defragmenting  with  Linux kernel versions < 
3.9 or ≥ 3.14-rc2 as well as with Linux stable kernel versions ≥ 
3.10.31, ≥ 3.12.12 or ≥ 3.13.4 will break up the reflinks of COW data 
(for example files copied with cp --reflink, snapshots or de-duplicated 
data)." Why does defragmenting not preserve reflinks and why was it removed?

-- 
George truly, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
This email does not constitute a legally binding contract

             reply	other threads:[~2025-05-29 23:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 23:52 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 [this message]
2025-05-30  0:27 ` Why does defragmenting break reflinks? Qu Wenruo
2025-05-30 22:41   ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
     [not found]   ` <3eabd123-e2a8-4554-b57b-0c84b713cd10@velocifyer.com>
2025-05-30 22:53     ` Qu Wenruo
2025-06-04 21:36   ` Ferry Toth
2025-06-04 21:54     ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-06-05  8:17       ` Christopher Snowhill

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=9d74d71f-b65d-4f06-adb3-18f7698edb8a@velocifyer.com \
    --to=velocifyer@velocifyer.com \
    --cc=linux-btrfs@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