Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #211977
| From | Judah Richardson <judahrichardson@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? |
| Date | 2019-07-31 16:10 +0200 |
| Message-ID | <ypXsJ-2hx-9@gated-at.bofh.it> (permalink) |
| References | <ypfL3-8rM-9@gated-at.bofh.it> <ypifU-1GP-7@gated-at.bofh.it> <ypUuR-du-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
This. From the Btfrs Gotchas page: Files with a lot of random writes can become heavily fragmented (10000+ > extents) causing thrashing on HDDs and excessive multi-second spikes of CPU > load on systems with an SSD or large amount a RAM. > > - On servers and workstations this affects databases and virtual > machine images. > - The nodatacow mount option > <https://btrfs.wiki.kernel.org/index.php/Mount_options> may be of > use here, with associated gotchas. > - On desktops this primarily affects application databases (including > Firefox and Chromium profiles, GNOME Zeitgeist, Ubuntu Desktop Couch, > Banshee, and Evolution's datastore.) > - Workarounds include manually defragmenting your home directory > using btrfs fi defragment. Auto-defragment (mount option autodefrag) should > solve this problem in 3.0. > - Symptoms include btrfs-transacti and btrfs-endio-wri taking up a lot > of CPU time (in spikes, possibly triggered by syncs). You can use filefrag > to locate heavily fragmented files (may not work correctly with > compression). > > On Wed, Jul 31, 2019 at 5:50 AM Mart van de Wege <mvdwege@gmail.com> wrote: > Stefan Monnier <monnier@iro.umontreal.ca> writes: > > >> Is it safe to use autodefrag for my use case? > > > > It sounds like it might be "safe" (the text doesn't actually say it's > > unsafe, but just that it has downsides). > > > > I do wonder why you'd want to do that, tho. Fragmentation is typically > > something that clueless Windows users worry about > > No. Fragmentation is an issue with all copy-on-write filesystems > (including ZFS, which avoids periodic defrag by keeping an enormous > amount of information in memory and doing defrag on the fly on that). > > Mart > > -- > "We will need a longer wall when the revolution comes." > --- AJS, quoting an uncertain source. > >
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? Judah Richardson <judahrichardson@gmail.com> - 2019-07-29 17:30 +0200
Re: Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? Stefan Monnier <monnier@iro.umontreal.ca> - 2019-07-29 20:10 +0200
Re: Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? David Wright <deblis@lionunicorn.co.uk> - 2019-07-29 23:50 +0200
Re: Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? Stefan Monnier <monnier@iro.umontreal.ca> - 2019-07-30 00:00 +0200
Re: Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? Mart van de Wege <mvdwege@gmail.com> - 2019-07-31 13:00 +0200
Re: Debian Buster: Is it safe to use on autodefrag on a Btrfs filesystem that is used for (Restic) backup only with no Btrfs snapshots or subvolumes? Judah Richardson <judahrichardson@gmail.com> - 2019-07-31 16:10 +0200
csiph-web