linux-ext4 - Re: [Bug 14830] When other IO is running sync times go to 10 to 20 minutes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-id: <6465E5ED-8392-4929-9FD6-EFCCA7D75E0B@sun.com>
Date:	Wed, 27 Jan 2010 12:43:57 -0700
From:	Andreas Dilger <adilger@....com>
To:	Andre Noll <maan@...temlinux.org>
Cc:	Michael Godfrey <godfrey@....stanford.edu>,
	linux-ext4@...r.kernel.org
Subject: Re: [Bug 14830] When other IO is running sync times go to 10 to 20
 minutes

On 2010-01-27, at 06:06, Andre Noll wrote:
> On 11:19, bugzilla-daemon@...zilla.kernel.org wrote:
>> After kill -9 of the sync run it took about 20 minutes before
>> it died.
>
> I was seeing similar behaviour on one of our servers, and changing
> the io scheduler to noop fixed things for me. So it seems to be an
> issue with cfq which is somehow triggered by ext4 but not by ext3.
>
> To change the IO scheduler, just execute
>
> 	echo noop > /sys/block/sda/queue/scheduler

Andre, could you please also test deadline instead of noop?  In  
general, deadline has nearly the same IO behaviour as noop, but still  
allows simple request merging and is generally a better option than  
noop.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html