From: ching <lsching17@gmail.com>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: enquiry about autodefrag option (resent)
Date: Mon, 17 Sep 2012 19:15:30 +0800 [thread overview]
Message-ID: <50570652.4060200@gmail.com> (raw)
I am testing btrfs for long-term storage and backup, and i would like
to know more about "autodefrag" option:
1. Will "autodefrag" option benefit ssd?
My understanding is:
autodrag -> number of extent decrease -> metadata decrease -> a
"healthier" filesystem in the long run
(P.S. I am aware that autodefrag will introduce extra write I/O)
2. AFAIK, "autodefrag" detects small random writes into files and
queues them up for an automatic defrag process, so the filesystem will
defragment itself while it's used.
If the system reboot/crash/remount-ro, will the autodefrag process
continue after resume?
next reply other threads:[~2012-09-17 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 11:15 ching [this message]
2012-09-19 11:28 ` enquiry about autodefrag option ching
2012-09-19 14:12 ` Liu Bo
2012-09-19 17:39 ` Martin Steigerwald
2012-09-20 14:05 ` David Sterba
2012-09-19 23:36 ` ching
2012-09-20 11:51 ` David Sterba
2012-09-20 21:03 ` ching
2012-09-24 15:50 ` David Sterba
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=50570652.4060200@gmail.com \
--to=lsching17@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).