From: Martin Spott <Martin.Spott@mgras.net>
To: linux-xfs@oss.sgi.com
Subject: Re: XFS and DPX files
Date: Mon, 14 Dec 2009 16:17:28 +0000 (UTC) [thread overview]
Message-ID: <hg5oeo$bh2$1@osprey.mgras.de> (raw)
In-Reply-To: 200911022258.35164@zmi.at
Michael Monnerie wrote:
> Don't mix up the controller write cache vs. disk write cache. The
> controller write cache should be on whenever you have a BBM installed,
> because this brings real performance, while the disk write cache should
> always be off in a production environment, because you will loose data
> on power fail, which nobody can recognize (the controller believes the
> sectors to be written already...)
I've been under the impression that "modern disks" (TM), at minimum the
server-type products, are supposed to re-use the remaining spin-energy
for generating the required power and thus writing the content of their
on-disk write cache to the disks.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-14 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 12:26 XFS and DPX files AndrewL733
2009-10-31 14:18 ` Emmanuel Florac
2009-10-31 14:37 ` AndrewL733
2009-10-31 16:48 ` Emmanuel Florac
2009-11-02 11:05 ` Michael Monnerie
2009-11-02 17:52 ` Emmanuel Florac
2009-11-02 21:50 ` AndrewL733
2009-11-02 22:26 ` Emmanuel Florac
2009-11-03 3:09 ` Eric Sandeen
2009-11-02 21:58 ` Michael Monnerie
2009-11-03 11:19 ` Emmanuel Florac
2009-11-03 20:58 ` Michael Monnerie
2009-12-14 16:17 ` Martin Spott [this message]
2009-12-14 17:49 ` Michael Weissenbacher
2009-11-02 21:34 ` Eric Sandeen
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='hg5oeo$bh2$1@osprey.mgras.de' \
--to=martin.spott@mgras.net \
--cc=linux-xfs@oss.sgi.com \
/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