From: Tejun Heo <htejun@gmail.com>
To: Eamonn Hamilton <EAMONN.HAMILTON@saic.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: FUA and DPO unsupported using sata_nv on MCP55?
Date: Mon, 09 Apr 2007 16:45:11 +0900 [thread overview]
Message-ID: <4619EF07.5090008@gmail.com> (raw)
In-Reply-To: <1175778811.5181.9.camel@ukabzc383.uk.saic.com>
Eamonn Hamilton wrote:
> Hi,
>
> I've got a couple of Samsung HD501LJ drives attached to a KN9 Ultra
> board using the MCp55 chipset, and I'm getting an NCQ depth of 0
> reported at boot, which as I understand it is because support for NCQ
> isn't in the sata_nv driver yet for this chipset.
>
> ata1.00: ATA-7, max UDMA7, 976773168 sectors: LBA48 NCQ (depth 0/32)
> ata2.00: ATA-7, max UDMA7, 976773168 sectors: LBA48 NCQ (depth 0/32)
Yeap.
> Later in the boot, however, I get
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> SCSI device sda: write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
>
> which as I understand it means my data ( plus the wifes picture
> archive! ) is at risk, as I have write cache enabled and barrier support
> is disabled because of the lack of FUA. Is this caused by my drives, or
> is there something I need to enable?
Nothing is in danger. FUA just speeds up barrier a tad bit. Doesn't
matter really.
--
tejun
next prev parent reply other threads:[~2007-04-09 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 13:13 FUA and DPO unsupported using sata_nv on MCP55? Eamonn Hamilton
2007-04-09 7:45 ` Tejun Heo [this message]
2007-04-09 8:24 ` Eamonn Hamilton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4619EF07.5090008@gmail.com \
--to=htejun@gmail.com \
--cc=EAMONN.HAMILTON@saic.com \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.