Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761450AbZC3Ukw (ORCPT ); Mon, 30 Mar 2009 16:40:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758626AbZC3Ukn (ORCPT ); Mon, 30 Mar 2009 16:40:43 -0400 Received: from rtr.ca ([76.10.145.34]:33070 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758561AbZC3Ukm (ORCPT ); Mon, 30 Mar 2009 16:40:42 -0400 Message-ID: <49D12E47.5050803@rtr.ca> Date: Mon, 30 Mar 2009 16:40:39 -0400 From: Mark Lord Organization: Real-Time Remedies Inc. User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: Michael Tokarev Cc: Jeff Garzik , Rik van Riel , Linus Torvalds , Ric Wheeler , "Andreas T.Auer" , Alan Cox , Theodore Tso , Stefan Richter , Matthew Garrett , Andrew Morton , David Rees , Jesper Krogh , Linux Kernel Mailing List Subject: Re: Linux 2.6.29 References: <49CD7B10.7010601@garzik.org> <49CD891A.7030103@rtr.ca> <49CD9047.4060500@garzik.org> <49CE2633.2000903@s5r6.in-berlin.de> <49CE3186.8090903@garzik.org> <49CE35AE.1080702@s5r6.in-berlin.de> <49CE3F74.6090103@rtr.ca> <20090329231451.GR26138@disturbed> <20090330003948.GA13356@mit.edu> <49D0710A.1030805@ursus.ath.cx> <20090330100546.51907bd2@the-village.bc.nu> <49D0A3D6.4000300@ursus.ath.cx> <49D0AA4A.6020308@redhat.com> <49D0EF1E.9040806@redhat.com> <49D0FD4C.1010007@redhat.com> <49D11BDD.70702@redhat.com> <49D1206E.7090809@garzik.org> <49D129B4.1060503@msgid.tls.msk.ru> <49D12B10.20805@rtr.ca> <49D12D26.7080203@garzik.org> In-Reply-To: <49D12D26.7080203@garzik.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 980 Lines: 32 Jeff Garzik wrote: > Mark Lord wrote: >> Michael Tokarev wrote: >>> >>> But are there drives out there that actually supports FUA? >> .. >> >> Most (or all?) current model Hitachi Deskstar drives have it. > > Depends on your source of information: if you judge from probe > messages, libata_fua==0 will imply !FUA-support. .. As your other post points out, lots of drives already support FUA, but libata deliberately disables it by default (due to the performance impact, similar to mounting a f/s with -osync). For the curious, you can use this command to see if your hardware has FUA: hdparm -I /dev/sd? | grep FUA It will show lines like this for the drives that support it: * WRITE_{DMA|MULTIPLE}_FUA_EXT Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/