All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Sundman <marcus@hibox.fi>
To: Jan Kara <jack@suse.cz>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
	Dave Chinner <david@fromorbit.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Debugging system freezes on filesystem writes
Date: Fri, 13 Sep 2013 09:35:05 +0300	[thread overview]
Message-ID: <5232B219.5020603@hibox.fi> (raw)
In-Reply-To: <20130912204647.GA6826@quack.suse.cz>

On 12.09.2013 23:46, Jan Kara wrote:
> On Thu 12-09-13 20:59:07, Marcus Sundman wrote:
>> On 12.09.2013 19:35, Jan Kara wrote:
>>> On Thu 12-09-13 18:08:13, Marcus Sundman wrote:
>>>> And can I somehow "reset" whatever it is that is making it worse so
>>>> that it becomes good again? That way I could spend maybe 1 hour once
>>>> every few months to get it back to top speed.
>>>> Any other ideas how I could make this (very expensive and fairly new
>>>> ZenBook) laptop usable?
>>>    Well, I believe if you used like 70% or less of the disk and regularly
>>> (like once in a few days) run fstrim command, I belive the disk performance
>>> should stay at a usable level.
>> At 128 GB it is extremely small as it is, and I'm really struggling
>> to fit all on it. Most of my stuff is on my NAS (which has almost 10
>> TB space), but still I need several code repositories and the
>> development environment and a virtual machine etc on this tiny 128
>> GB thing.
>    I see. I have like 70 GB disk and 50% of it are free :) But I have test
> machines with much larger drives where I have VMs etc. This one is just
> for email and coding.
>
>> So, if I used some other filesystem, might that allow me to use a
>> larger portion of the SSD without this degradation? Or with a much
>> slower rate of degradation?
>    You might try f2fs. That is designed for low end flash storage so it
> might work better than ext4. But it is a new filesystem so backup often.
>
>> And at some point it will become unusable again, so what can I do
>> then? If I move everything to my NAS (and maybe even re-create the
>> filesystem?) and move everything back, might that get rid of the FTL
>> fragmentation?
>    Yes, that should get rid of it. But since you have only a few GB free,
> I'm afraid the fragmentation will reappear pretty quickly. But I guess it's
> worth a try.
>
>> Or could I somehow defragment the FTL without moving away everything?
>    I don't know about such way.

How about triggering the garbage collection on the drive, is that possible?


- Marcus


  reply	other threads:[~2013-09-13  6:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28 22:39 Debugging system freezes on filesystem writes Marcus Sundman
2012-11-01 19:01 ` Jan Kara
2012-11-02  2:19   ` Marcus Sundman
2012-11-07 16:17     ` Jan Kara
2012-11-08 23:41       ` Marcus Sundman
2012-11-09 13:12         ` Marcus Sundman
2012-11-13 13:51           ` Jan Kara
2012-11-16  1:11             ` Marcus Sundman
2012-11-21 23:30               ` Jan Kara
2012-11-27 16:14                 ` Marcus Sundman
2012-12-05 15:32                   ` Jan Kara
2013-02-20  8:42                     ` Marcus Sundman
2013-02-20 11:40                       ` Marcus Sundman
2013-02-22 20:51                         ` Jan Kara
2013-02-22 23:27                           ` Marcus Sundman
2013-02-24  0:12                             ` Dave Chinner
2013-02-24  1:20                               ` Theodore Ts'o
2013-02-26 18:41                                 ` Marcus Sundman
2013-02-26 22:17                                   ` Theodore Ts'o
2013-02-26 23:17                                   ` Jan Kara
2013-09-12 12:57                                     ` Marcus Sundman
2013-09-12 13:10                                       ` Jan Kara
2013-09-12 13:47                                         ` Marcus Sundman
2013-09-12 14:39                                           ` Jan Kara
2013-09-12 15:08                                             ` Marcus Sundman
2013-09-12 16:35                                               ` Jan Kara
2013-09-12 17:59                                                 ` Marcus Sundman
2013-09-12 20:46                                                   ` Jan Kara
2013-09-13  6:35                                                     ` Marcus Sundman [this message]
2013-09-13 20:54                                                       ` Jan Kara
2013-09-14  2:41                                                   ` Theodore Ts'o
2013-09-15 19:19                                                     ` Marcus Sundman
2013-09-16  0:06                                                       ` Theodore Ts'o
2013-02-25 13:05                             ` Jan Kara

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=5232B219.5020603@hibox.fi \
    --to=marcus@hibox.fi \
    --cc=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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.