From: Boris Maryshev <boris.maroshev@itcollege.ee>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Seagate Barracuda 7200.7 write cache?
Date: Tue, 13 Jul 2004 11:48:29 +0300 [thread overview]
Message-ID: <200407131148.29808.boris.maroshev@itcollege.ee> (raw)
In-Reply-To: <ccvpdp$q0e$1@wolfberry.srv.cs.cmu.edu>
On Tuesday 13 July 2004 11:25, David Eckhardt wrote:
> Am I being overly paranoid?
>
> http://www.seagate.com/docs/pdf/datasheet/disc/ds_barracuda7200.7.pdf
> is the "data sheet" for the SATA version of the Seagate Barracuda.
>
> Section 4.3.2 ("Set Features command") on logical page 31 (physical
> page 41) seems to indicate that the drive defaults to handling sector
> writes via a write-back RAM cache, which the host OS can disable.
>
> Is it just me or is this a very bad default except (maybe) for
> battery-backed systems? Is this a standard thing in IDE disks
> (either the feature number or the default setting), something
> Plan 9 should watch out for, nothing for me to worry my pretty
> little head about, ...?
It isn't enabled by default on all IDE HDDs AFAIK. Some recommend to enable
it, because you get increased throughput, but some UNIX vendors do not, as
you can get filesystem corruption in case of power failure. Journalling
doesn't help here either IIRC.
>
> Dave Eckhardt
Boris Maryshev
--
A banker is a fellow who lends you his umbrella when the sun is shining
and wants it back the minute it begins to rain.
-- Mark Twain
next prev parent reply other threads:[~2004-07-13 8:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 8:25 David Eckhardt
2004-07-13 8:48 ` Boris Maryshev [this message]
2004-07-16 17:03 ` David Eckhardt
2004-07-16 18:52 ` ron minnich
2004-07-16 19:22 ` Brantley Coile
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=200407131148.29808.boris.maroshev@itcollege.ee \
--to=boris.maroshev@itcollege.ee \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).