From: "Theodore Ts'o" <tytso@mit.edu>
To: Marcus Sundman <marcus@hibox.fi>
Cc: Jan Kara <jack@suse.cz>, Dave Chinner <david@fromorbit.com>,
linux-kernel@vger.kernel.org
Subject: Re: Debugging system freezes on filesystem writes
Date: Fri, 13 Sep 2013 22:41:08 -0400 [thread overview]
Message-ID: <20130914024108.GA10740@thunk.org> (raw)
In-Reply-To: <523200EB.7000202@hibox.fi>
On Thu, Sep 12, 2013 at 08:59:07PM +0300, Marcus Sundman wrote:
>
> 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.
>
> 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?
What model are you using? It's possible that your flash device was
designed as a cache driver for windows. As such, it might have been
optimized for a read-mostly workload and not something for a lot of
random small writes.
The f2fs file system is designed for crappy flash drives with crappy
FTL's, so it might work be better for you. But let me ask you this
--- how much is your data worth? How much would it cost to replace
your flash device with something better?
I tend to get very nervous with crappy storage devices, and it sounds
like your flash drive isn't a particularly good one. I'd strongly
suggest doing regular backups, because when flash devices die, they
can die in extremely catastrphic ways.
Regards,
- Ted
next prev parent reply other threads:[~2013-09-14 2:41 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
2013-09-13 20:54 ` Jan Kara
2013-09-14 2:41 ` Theodore Ts'o [this message]
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=20130914024108.GA10740@thunk.org \
--to=tytso@mit.edu \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus@hibox.fi \
/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