linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nebojsa Trpkovic <trx.lists@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: "data=writeback" and TRIM don't get along
Date: Thu, 08 Apr 2010 18:21:49 +0200	[thread overview]
Message-ID: <4BBE029D.9030303@gmail.com> (raw)
In-Reply-To: <4BBDF6F4.2020208@redhat.com>

On 04/08/10 17:32, Eric Sandeen wrote:
> Well, you might just keep in mind that:
> 
> 1) trimming these small amounts has actually looked very inefficient, and
> 2) data=writeback really isn't very safe in the face of a crash or power loss, and
> 3) hopefully we'll have a better trim solution eventually.

1) I understand that big TRIMs are better then small ones, but skipping
some TRIMs completely would lead to slow but sure drive degradation as
drive would have less and less spare space for wear leveling.

2) Yes, I'm aware of possible data=writeback inconsistency, but I've
tried to let IO scheduler to merge and reorganize as many writes as it
can, all to avoid small writes to SSD which are main cause of write
amplification.

3) I'll stick with no data=writeback for the time being. I guess I'm
doing just fine even without it. :)


One more noob quotestion completely out-of-topic:
Will md layer pass TRIM command to drive if one has ext4 on linux
software RAID 0/1/5 ?

Nebojsa

  reply	other threads:[~2010-04-08 16:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  0:50 "data=writeback" and TRIM don't get along Nebojsa Trpkovic
2010-04-08  1:22 ` Eric Sandeen
2010-04-08  1:37   ` Nebojsa Trpkovic
2010-04-08  4:10     ` Eric Sandeen
2010-04-08  4:37       ` Eric Sandeen
2010-04-08  4:47         ` Eric Sandeen
2010-04-08 11:48           ` Nebojsa Trpkovic
2010-04-08 15:32             ` Eric Sandeen
2010-04-08 16:21               ` Nebojsa Trpkovic [this message]
2010-04-08 16:34                 ` Eric Sandeen
2010-04-08  7:17     ` Dmitry Monakhov
2010-04-08 11:47       ` Nebojsa Trpkovic

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=4BBE029D.9030303@gmail.com \
    --to=trx.lists@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).