Messages in this thread | | | Date | Sun, 15 Sep 2013 22:19:41 +0300 | From | Marcus Sundman <> | Subject | Re: Debugging system freezes on filesystem writes |
| |
On 14.09.2013 05:41, Theodore Ts'o wrote: > 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.
It's a SanDisk SSD U100.
> The f2fs file system is designed for crappy flash drives with crappy > FTL's, so it might work be better for you.
OK, I'll probably try it when I have time to switch.
> 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?
A lot. I have lsyncd running here most of the time, backing up to my raid-z NAS which in turn uses a versioned off-site backup system. Anyway, this is an Asus ZenBook computer and can't be opened. Well, it can, but that will void the warranty at the very least.
- Marcus
| |