Re: Debugging system freezes on filesystem writes

[Jan Kara]

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.

								Honza
-- 
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/