From: Gim Leong Chin <chingimleong@yahoo.com.sg>
To: Emmanuel Florac <eflorac@intellique.com>,
Roger Willcocks <roger@filmlight.ltd.uk>
Cc: Steve Brooks <sjb14@st-andrews.ac.uk>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: Advice needed with file system corruption
Date: Tue, 9 Aug 2016 04:02:55 +0000 (UTC) [thread overview]
Message-ID: <592673683.10446004.1470715375850.JavaMail.yahoo@mail.yahoo.com> (raw)
In-Reply-To: <20160808174427.24d8272c@harpe.intellique.com>
[-- Attachment #1.1: Type: text/plain, Size: 1066 bytes --]
From: Emmanuel Florac <eflorac@intellique.com>
To: Roger Willcocks <roger@filmlight.ltd.uk>
Cc: Steve Brooks <sjb14@st-andrews.ac.uk>; xfs@oss.sgi.com
Sent: Monday, 8 August 2016, 23:44
Subject: Re: Advice needed with file system corruption
Le Mon, 08 Aug 2016 16:38:11 +0100
Roger Willcocks <roger@filmlight.ltd.uk> écrivait:
> >
> > Late to the game, I just wanted to remark that I've unfortunately
> > verified many times that write activity during rebuilds on Adaptec
> > RAID controllers often creates corruption. I've reported that to
> > Adaptec, but they don't seem to care much...
> >
>
> It seems like explicitly disabling individual disk drives write-back
> cache somewhat mitigates the effect.
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.
[-- Attachment #1.2: Type: text/html, Size: 2925 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-08-09 4:03 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 [this message]
2016-08-09 12:40 ` Carlos E. R.
2016-08-09 15:43 ` Gim Leong Chin
2016-08-09 21:26 ` Dave Chinner
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=592673683.10446004.1470715375850.JavaMail.yahoo@mail.yahoo.com \
--to=chingimleong@yahoo.com.sg \
--cc=eflorac@intellique.com \
--cc=roger@filmlight.ltd.uk \
--cc=sjb14@st-andrews.ac.uk \
--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