From: Emmanuel Florac <eflorac@intellique.com>
To: Ferenc Kovacs <tyra3l@gmail.com>, xfs@oss.sgi.com
Subject: Re: easily reproducible filesystem crash on rebuilding array
Date: Thu, 17 Sep 2015 08:17:57 +0200 [thread overview]
Message-ID: <20150917081757.48aaf891@galadriel.home> (raw)
In-Reply-To: <CAH-PCH7W4yTDRhAiKQwN_wQJMx2sTitQYrLNPcLYHvJRucXBjA@mail.gmail.com>
Le Wed, 16 Sep 2015 15:50:13 +0200 vous écriviez:
> Hi,
>
> have you found a resolution to your problem?
> we are facing a similar issue(fs corruption every time when
> rebuilding the array) with an Adaptec Series 8 Raid controller.
The problem didn't occur anymore after I deactivated
individual disks write caching in the "controller settings". This is
only adjustable through the RAID BIOS though, not through arcconf
apparently.
This seems to apply to all of 5xx5, 6xx5, 7xx5 series. I never rebuilt
an array with a 8xx5 yet (though I have some). I don't know why this is
not the default settings (default keeps the disks write cache active
instead). Adaptec support and engineering deny that the problem exists,
though I've sent many logs and defined a test procedure that allow to
reproduce the problem reliably enough.
Thanks god for XFS. ext4 is completely unaware of the corruptions, but
they're present nonetheless (md5summing files before, during and
after rebuild)...
BTW I'm curious, where did you find this address? This isn't the one
I'm using on the XFS mailing list...
cheers
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next parent reply other threads:[~2015-09-17 6:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH-PCH7W4yTDRhAiKQwN_wQJMx2sTitQYrLNPcLYHvJRucXBjA@mail.gmail.com>
2015-09-17 6:17 ` Emmanuel Florac [this message]
2015-09-17 7:21 ` easily reproducible filesystem crash on rebuilding array Ferenc Kovacs
2015-09-17 11:17 ` Emmanuel Florac
2014-12-11 11:39 Emmanuel Florac
2014-12-11 15:52 ` Eric Sandeen
2014-12-15 12:07 ` Emmanuel Florac
2014-12-15 12:25 ` Emmanuel Florac
2014-12-15 20:10 ` Dave Chinner
2014-12-16 7:56 ` Christoph Hellwig
2014-12-16 11:38 ` Emmanuel Florac
2014-12-16 17:21 ` Emmanuel Florac
2014-12-16 11:34 ` Emmanuel Florac
2014-12-16 19:58 ` Dave Chinner
2014-12-17 11:21 ` Emmanuel Florac
2014-12-18 15:40 ` Emmanuel Florac
2014-12-18 22:58 ` Dave Chinner
2014-12-19 11:57 ` Emmanuel Florac
2014-12-19 23:06 ` Dave Chinner
2015-01-13 11:21 ` Emmanuel Florac
2015-01-13 13:59 ` Emmanuel Florac
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=20150917081757.48aaf891@galadriel.home \
--to=eflorac@intellique.com \
--cc=tyra3l@gmail.com \
--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