lkml.org 
[lkml]   [2011]   [Sep]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: Abysmal I/O scheduling with dm-crypt
From
> On Tue 30-08-11 09:14:07, martin f krafft wrote:
>> People not running dm-crypt seem unable to reproduce this problem,
>> making me think that it must be due to dm-crypt, and I wouldn't find
>> it hard to imagine, because dm-crypt basically shields the
>> I/O-scheduler of the kernel, doesn't it? Worse, it probably doesn't
>> make any effort of scheduling I/O itself. Note: I know very little
>> about the internals, so please correct me if I am wrong.

No, it's not specific to dm-crypt, these kinds of annoying IO hangs happen
on bare drives, MD arrays or DM-* setups.

There's a number of causes - including firefox history updates and the
abuse of create/sync/rename due to metadata hitting disk before data.

There's not going to be any movement on that front, I'm afraid, see
"Don't fear the fsync" (reproduced at
http://www.linuxfoundation.org/news-media/blogs/browse/2009/03/don%E2%80%99t-fear-fsync
, the original site couldn't be reached while I'm writing this).

You can either throw more hardware at it, or use libeatmydata to
disable fsync across the board. Maybe, eventually, a filesystem will
be written that can manage an atomic replace without fsync(). Don't
hold your breath.


\
 
 \ /
  Last update: 2011-09-08 04:53    [W:0.054 / U:0.156 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site