From: "Christopher Snowhill" <chris@kode54.net>
To: 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 <velocifyer@velocifyer.com>,
"Ferry Toth" <fntoth@gmail.com>, "Qu Wenruo" <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: Why does defragmenting break reflinks?
Date: Thu, 05 Jun 2025 01:17:19 -0700 [thread overview]
Message-ID: <DAEG9AKPBKFN.2ZRRNL0ROETEL@kode54.net> (raw)
In-Reply-To: <1d6ac208-a08a-47e4-8c9f-9f99bd244146@velocifyer.com>
On Wed Jun 4, 2025 at 2:54 PM PDT, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 wrote:
> On 6/4/25 17:36, Ferry Toth wrote:
>> Actually this makes defrag a very dangerous operation on disks with
>> many snapshots (> 20). When you would defrag each snapshot suddenly
>> your 5% full disk would be 100%.
>
> This actualy happend to me once because i forgot i had snapshots.
Greater than 20 is a lot of snapshots? I guess I should stop using
things like Snapper on my systems, then. It *defaults* to hourly
snapshots of every subvolume you activate it on, pruned to the last 24
hours, so that's 24 alone. Then it keeps midnight for every day going
back several weeks.
prev parent reply other threads:[~2025-06-05 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 23:52 Why does defragmenting break reflinks? 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-05-30 0:27 ` 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 [this message]
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=DAEG9AKPBKFN.2ZRRNL0ROETEL@kode54.net \
--to=chris@kode54.net \
--cc=fntoth@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=velocifyer@velocifyer.com \
--cc=wqu@suse.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