Date: Mon, 07 Nov 2005 14:56:45 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> Cc: freebsd-ports@freebsd.org, le@freebsd.org Subject: Re: vinum, 5.x performance, ... (was: Re: ANNOUNCE: GNOME 2.12.1 has been merged into the ports tree) Message-ID: <20051107145645.rav7hhtlsggk4sss@netchild.homeip.net> In-Reply-To: <20051107122458.27a1f9e7@it.buh.tecnik93.com> References: <20051106.131413.122956532.yasu@utahime.org> <1131176568.3960.20.camel@shumai.marcuscom.com> <20051106.131413.122956532.yasu@utahime.org> <op.szszvnn89aq2h7@mezz.mezzweb.com> <ZhqaDxv9wJ@dmeyer.dinoex.sub.org> <20051107111800.e199ndcxa8s0c444@netchild.homeip.net> <20051107122458.27a1f9e7@it.buh.tecnik93.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Ion-Mihai Tetcu <itetcu@people.tecnik93.com> wrote: > On Mon, 07 Nov 2005 11:18:00 +0100 > Alexander Leidinger <Alexander@Leidinger.net> wrote: > >> > - and performaces is a nightmare on atapi harddisks >> >> AFAIR 4.x enables the write cache (bad if there's a power failure in >> the soft-updates case, since without native command queueing the >> drivers may reorder writes witout the possibility to notify >> soft-updates about it), > > So on NCQ disks write_caching should be safe from consistency > point-of-view ? AFAIK: Enabling the write cache doesn't mean you use NCQ. So just because your drive is able to do NCQ, you shouldn't enable the write cache. If your controller, your disk and the OS is able to use NCQ, and you enable the use of NCQ, then everything is fine... assuming the drive doesn't lie to you. AFAIR there are or there where some drives which lie(d), but I don't remember the details. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 If your parents don't have kids, neither will you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051107145645.rav7hhtlsggk4sss>