All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: autodefrag by default, was: Lots of harddrive chatter
Date: Sun, 21 Jul 2013 10:20:48 -0600	[thread overview]
Message-ID: <09A15D35-4874-4650-93F1-1E151076C498@colorremedies.com> (raw)
In-Reply-To: <pan$3c802$83940fc4$86279b1e$4ddf0e4e@cox.net>


On Jul 21, 2013, at 4:38 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> 
> What I'd suggest is to turn on the btrfs autodefrag mount option, and to 
> do it *BEFORE* you start installing stuff on the filesystem.

Is there a good reason why autodefrag is not a default mount option?


>  I believe 
> it's a known issue that a number of distro installers (what arch does I'm 
> not sure) tend to fragment their files pretty badly right off the bat if 
> you let them.  This would happen if they write data into an existing 
> file, perhaps because they install a package and then customize the config 
> files, or if they don't write whole files at once.  And a lot of btrfs 
> installs don't turn on the autodefrag option when they do thet first auto-
> mount to install stuff.  

Some installer teams are understandably reluctant to use non-default mount options.

Chris Murphy

  reply	other threads:[~2013-07-21 16:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 15:15 Lots of harddrive chatter on after booting with btrfs on root (slow boot) Jason Russell
2013-07-20 15:52 ` George Mitchell
2013-07-20 22:14 ` Lukas Martini
2013-07-20 22:47 ` Gabriel de Perthuis
2013-07-21 10:38   ` Duncan
2013-07-21 16:20     ` Chris Murphy [this message]
     [not found]   ` < pan$3c802$83940fc4$86279b1e$4ddf0e4e@cox.net>
     [not found]     ` < 09A15D35-4874-4650-93F1-1E151076C498@colorremedies.com>
2013-07-21 22:01       ` autodefrag by default, was: Lots of harddrive chatter Duncan
2013-07-21 23:44         ` George Mitchell
2013-07-22  3:37           ` Shridhar Daithankar
2013-07-22  3:53             ` George Mitchell
2013-07-22  4:11               ` Shridhar Daithankar
     [not found]   ` < pan$7e18b$b2c36a61$b1f22c8c$6c61ba6e@cox.net>
     [not found]     ` <51EC7249.3010005@chinilu.com >
2013-07-22 12:09       ` Duncan

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=09A15D35-4874-4650-93F1-1E151076C498@colorremedies.com \
    --to=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.