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:	Mon, 21 Apr 2008 14:44:45 -0400
From:	Ric Wheeler <ric@....com>
To:	Eric Sandeen <sandeen@...hat.com>
CC:	Andi Kleen <andi@...stfloor.org>, Theodore Tso <tytso@....edu>,
	Alexey Zaytsev <alexey.zaytsev@...il.com>,
	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Rik van Riel <riel@...riel.com>
Subject: Re: Mentor for a GSoC application wanted (Online ext2/3 filesystem
 checker)


Eric Sandeen wrote:
> Ric Wheeler wrote:
>> Andi Kleen wrote:
>>> On Mon, Apr 21, 2008 at 12:42:42AM +0100, Jamie Lokier wrote:
>>>> Andi Kleen wrote:
>>>>> [LVM] always disables barriers if you don't apply a so far unmerged
>>>>> patch that enables them in some special circumstances (only single
>>>>> backing device)
>>>> (I continue to be surprised at the un-safety of Linux fsync)
>>> Note barrier less does not necessarily always mean unsafe fsync,
>>> it just often means that.
>>>
>>> Also surprisingly lot more syncs or write cache off tend to lower the MTBF 
>>> of your disk significantly, so "unsafer" fsync might actually be more safe
>>> for your unbackuped data.
>>>
>> Hi Andi,
>>
>> Where did you get this data?
>>
>> I have never heard that using more barrier operations lowers the reliability or 
>> the MTBF of a drive and I look at a fairly huge population when doing this ;-)
> 
> Ric, what about the other part - turning write cache off?  I've also
> heard it suggested that this might hurt drive lifespan, and it sorta
> makes sense, I assume it keeps the head working harder...
> 
> -Eric

Turning the drive write cache off is the default case for most RAID products 
(including our mid and high end arrays).

I have not seen an issue with drives wearing out with either setting (cache 
disabled or enabled with barriers).

The theory does make some sense, but does not map into my experience ;-)

ric
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ