From: Dave Chinner <david@fromorbit.com>
To: "Carlos E. R." <robin.listas@telefonica.net>
Cc: XFS mail list <xfs@oss.sgi.com>
Subject: Re: Advice needed with file system corruption
Date: Wed, 10 Aug 2016 07:26:07 +1000 [thread overview]
Message-ID: <20160809212607.GH19025@dastard> (raw)
In-Reply-To: <7faf941c-2188-589d-b624-9fedb22dee40@telefonica.net>
On Tue, Aug 09, 2016 at 02:40:26PM +0200, Carlos E. R. wrote:
> On 2016-08-09 06:02, Gim Leong Chin wrote:
>
> > Drives connected to RAID controllers with battery backed cache should
> > have their caches "disabled" (they are really set to write through mode
> > instead). By the way, I found out in lab testing that 7200 RPM SATA
> > drives suffer a big performance loss when doing sequential writes in
> > cache write through mode.<http://oss.sgi.com/mailman/listinfo/xfs>
>
> If you disable the disk internal cache, as a consequence you also
> disable the disk internal write optimizations. It has to be much slower
> at writing. It seems to me obvious.
This is why decent HW RAID controllers have a large non volatile
write cache - the caching is done in the controller where it is safe
from power loss, not in the drive where it is unsafe. Write
optimisations happen at the RAID controller level, not at the
individual drive level.
As for 10/15krpm SAS drive performance, they generally are only
slower in microbenchmark situations (e.g. sequential single sector
writes) when the write cache is disabled. These sorts of loads
aren't typically seen in the real world, so for most people there is
little difference in performance on high end enterprise SAS drives
when changing the cache mode....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-09 21:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 12:27 Advice needed with file system corruption Steve Brooks
2016-07-14 13:05 ` Carlos Maiolino
2016-07-14 13:57 ` Steve Brooks
2016-07-14 14:17 ` Carlos Maiolino
2016-07-14 23:33 ` Dave Chinner
2016-08-08 14:11 ` Emmanuel Florac
2016-08-08 15:38 ` Roger Willcocks
2016-08-08 15:44 ` Emmanuel Florac
2016-08-09 4:02 ` Gim Leong Chin
2016-08-09 12:40 ` Carlos E. R.
2016-08-09 15:43 ` Gim Leong Chin
2016-08-09 21:26 ` Dave Chinner [this message]
2016-08-08 16:16 ` Steve Brooks
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=20160809212607.GH19025@dastard \
--to=david@fromorbit.com \
--cc=robin.listas@telefonica.net \
--cc=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