linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: piorunz <piorunz@gmx.com>
To: linux-btrfs@vger.kernel.org
Subject: fstab autodegrag with 5.10 & 5.15 kernels, Debian?
Date: Thu, 27 Jan 2022 15:25:30 +0000	[thread overview]
Message-ID: <10e51417-2203-f0a4-2021-86c8511cc367@gmx.com> (raw)

Hi all,

Is it safe & recommended to run autodefrag mount option in fstab?
I am considering two machines here, normal desktop which has Btrfs as
/home, and server with VM and other databases also btrfs /home. Both
Btrfs RAID10 types. Both are heavily fragmented. I never defragmented
them, in fact. I run Debian 11 on server (kernel 5.10) and Debian
Testing (kernel 5.15) on desktop.

Running manual defrag on server machine, like:
sudo btrfs filesystem defrag -v -t4G -r /home
takes ages and can cause 120 second timeout kernel error in dmesg due to
service timeouts. I prefer to autodefrag gradually, overtime, mount
option seems to be good for that.

My current fstab mounting:

noatime,space_cache=v2,compress-force=zstd:3 0 2

Will autodefrag break COW files? Like I copy paste a file and I save
space, but defrag with destroy this space saving?
Also, will autodefrag compress files automatically, as mount option
enforces (compress-force=zstd:3)?

Any suggestions welcome.


--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

             reply	other threads:[~2022-01-27 15:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 15:25 piorunz [this message]
2022-01-27 21:14 ` fstab autodegrag with 5.10 & 5.15 kernels, Debian? Chris Murphy
2022-01-27 22:45 ` Qu Wenruo
2022-01-28 11:55 ` Kai Krakow
2022-01-28 12:14   ` piorunz
2022-01-28 12:42     ` Qu Wenruo
2022-01-29  1:37       ` piorunz
2022-01-28 13:00   ` Qu Wenruo
2022-01-28 15:48     ` Kai Krakow
2022-01-28 16:05   ` Remi Gauvin
2022-01-28 18:01     ` Kai Krakow
2022-01-28 18:09       ` Remi Gauvin
2022-01-28 18:23         ` Kai Krakow
2022-01-28 18:29           ` Remi Gauvin
2022-01-28 18:44             ` Roman Mamedov
2022-01-28 18:33           ` Remi Gauvin
2022-01-28 22:42     ` Forza
2022-01-28 16:25   ` Remi Gauvin
2022-01-28 18:07     ` Kai Krakow
2022-01-28 18:23       ` Remi Gauvin
2022-01-29  1:33 ` piorunz

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=10e51417-2203-f0a4-2021-86c8511cc367@gmx.com \
    --to=piorunz@gmx.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;
as well as URLs for NNTP newsgroup(s).