linux-kernel - Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 25 Nov 2008 15:22:35 -0600
From:	Eric Sandeen <sandeen@...deen.net>
To:	Stian Jordet <liste@...det.net>
CC:	Sven-Haegar Koch <haegar@...net.de>, xfs@....sgi.com,
	linux-kernel@...r.kernel.org
Subject: Re: Extreme slowness with xfs [WAS: Re: Slowness with new pc]

Stian Jordet wrote:
> ti., 25.11.2008 kl. 01.09 +0100, skrev Sven-Haegar Koch:
>> I had the same problem when I tried it on my laptop (T60) - using it on 
>> the unencrypted root filesystem (with /usr/src) took ages, using it on 
>> the LUKS encrypted /home was blasing fast - on the same disk.
>>
>> This test was some time ago with something like 2.6.20 or 2.6.24 - I 
>> gave up and reformatted / with ext3 as I needed the machine.
>>
>> I think barriers were the problem, they seem to cost performance like 
>> hell, especially for operations with many small files. My laptop used 
>> barriers for xfs on the direct partition, but not on crypto drivermapper 
>> mounts.
>>
>> So perhaps try mounting with nobarrier and see if the speed problem goes 
>> away - but know that you sacrifice some crash-resilience when doing so.
> 
> Barriers were the problem indeed. My old system had no problems with
> barriers, but here it did an incredible difference.

Depending on the old system, perhaps its storage did not allow the
barriers to be honored, so after xfs saw a test barrier write fail at
mount time, it disabled them ... you'd see a message if that were the
case, FWIW.

-Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/