linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Linux fs Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: number of subvolumes
Date: Thu, 31 Aug 2017 07:18:23 -0400	[thread overview]
Message-ID: <0b8ff573-ae13-121a-dd14-29d0de72ef58@gmail.com> (raw)
In-Reply-To: <20170831064916.GA5783@rus.uni-stuttgart.de>

On 2017-08-31 02:49, Ulli Horlacher wrote:
> On Thu 2017-08-24 (18:45), Peter Grandi wrote:
> 
>> As usual with Btrfs, there are corner cases to avoid: 'defrag'
>> should be done before 'balance'
> 
> Good hint. So far I did it the other way: balance before defrag.
> I will switch.
For reference, the reason to do things this way is that defragmenting a 
filesystem may result in undoing some of the work balance did.
> 
> 
>> and with compression switched off
> 
> I have filesystems with compress mount option:
> 
> framstag@fex:~: grep /local /etc/fstab
> LABEL=local /local btrfs  defaults,compress,user_subvol_rm_allowed 0 2
> 
> and a weekly cronjob, which does a defrag and balance.
> I cannot disable compression.
> Any hint here?
Having compression enabled causes no issues with defray and balance. 
There appears to be a prevalent belief however that defrag is pointless 
if you're using compression, probably because some versions of 
`filefrag` don't report compressed extents properly (they list each 128k 
compressed unit as one extent, which is wrong).
> 
> 
>> I prefer dump-and-reload.
> 
> What do you mean by this?
I believe he means to copy everything off the filesystem, recreate it, 
and copy everything back in.  That will actually get you much closer to 
an optimal layout than a defrag=balance cycle, but it also takes a long 
time, requires extra space, and the layout will usually become 
sub-optimal almost immediately when you start writing to the filesystem.

  reply	other threads:[~2017-08-31 11:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 13:22 netapp-alike snapshots? Ulli Horlacher
2017-08-22 13:44 ` Peter Becker
2017-08-22 14:24   ` Ulli Horlacher
2017-08-22 16:08     ` Peter Becker
2017-08-22 16:48       ` Ulli Horlacher
2017-08-22 16:45     ` Roman Mamedov
2017-08-22 16:57       ` Ulli Horlacher
2017-08-22 17:19         ` A L
2017-08-22 18:01           ` Ulli Horlacher
2017-08-22 18:36             ` Peter Grandi
2017-08-22 20:48               ` Ulli Horlacher
2017-08-23  7:18                 ` number of subvolumes Ulli Horlacher
2017-08-23  8:37                   ` A L
2017-08-23 16:48                     ` Ferry Toth
2017-08-24 17:45                       ` Peter Grandi
2017-08-31  6:49                         ` Ulli Horlacher
2017-08-31 11:18                           ` Austin S. Hemmelgarn [this message]
2017-08-31 14:38                             ` Michał Sokołowski
2017-08-31 16:18                               ` Duncan
2017-09-01 10:21                                 ` ein
2017-09-01 11:47                                   ` Austin S. Hemmelgarn
2017-08-24 19:40                       ` Marat Khalili
2017-08-24 21:56                         ` Ferry Toth
2017-08-25  5:54                           ` Chris Murphy
2017-08-25 11:45                           ` Austin S. Hemmelgarn
2017-08-25 12:55                             ` Ferry Toth
2017-08-25 19:18                               ` Austin S. Hemmelgarn
2017-08-23 12:11                   ` Peter Grandi
2017-08-22 21:53               ` user snapshots Ulli Horlacher
2017-08-23  6:28                 ` Dmitrii Tcvetkov
2017-08-23  7:16                   ` Dmitrii Tcvetkov
2017-08-23  7:20                     ` Ulli Horlacher
2017-08-23 11:42                       ` Peter Grandi
2017-08-23 21:13                         ` Ulli Horlacher
2017-08-25 11:28                           ` Austin S. Hemmelgarn
2017-08-22 17:36         ` netapp-alike snapshots? Roman Mamedov
2017-08-22 18:10           ` Ulli Horlacher
2017-09-09 13:26 ` Ulli Horlacher
2017-09-09 13:36   ` Marc MERLIN
2017-09-09 13:44     ` Ulli Horlacher
2017-09-09 19:43       ` Andrei Borzenkov
2017-09-09 19:52         ` Ulli Horlacher
2017-09-10  7:10           ` A L
2017-09-10 14:54         ` Marc MERLIN

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=0b8ff573-ae13-121a-dd14-29d0de72ef58@gmail.com \
    --to=ahferroin7@gmail.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).