From: norritt@t-online.de
To: linux-ext4@vger.kernel.org
Subject: Ongoing data reorganization/defragmentation?
Date: Wed, 12 Sep 2012 18:36:24 +0200 [thread overview]
Message-ID: <5050BA08.80709@bytefortress.de> (raw)
Ongoing data reorganization/defragmentation?
In my efforts to optimize an ext4 for usage on SSDs, I have found
information on the web about ext4 I've not been able to verify.
From what I've found out it's a good idea to:
- mount with noatime, discard (if drive supports trim)
- put /tmp and maybe /var on a tempfs
- set vm.swappiness=1, vm.vfs_cache_pressure=50 (to utilize RAM rather
than the disk)
Another proposal found is to disable journaling what I personally won't do.
I also know from the ext4 dcumentation, that ext4 is written to support
online defragmentation. I've read several rumours on forums and blogs
that indicate ext4 is doing some kind of "ongoing data reorganisations
or defragmentation" in the background, in case the mechanisms to prevent
fragmentation in the first place failed for some reason (i.e. when a fs
is running out of free space). I did not find any credible information
to back up these claims, that ext4 is actively reorganizing data, but I
didn't find any information that prove these claims wrong either.
So my question is, does ext4 reorganize data when it encounters
fragmented files? If so, is there a way to disable that feature which
would not do any good on SSDs? Is there anything else to consider when
using ext4 on SSDs, except the things I mentioned above?
Please cc me since I'm not subscribed, thanks!
Regards Nor
next reply other threads:[~2012-09-12 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 16:36 norritt [this message]
2012-09-12 17:35 ` Ongoing data reorganization/defragmentation? Andreas Dilger
2012-09-13 12:20 ` norritt
2012-09-12 18:15 ` Lukáš Czerner
2012-09-13 12:54 ` norritt
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=5050BA08.80709@bytefortress.de \
--to=norritt@t-online.de \
--cc=linux-ext4@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).