From: Dark Penguin <darkpenguin@yandex.ru>
To: Edward Kuns <eddie.kuns@gmail.com>, linux-raid@vger.kernel.org
Subject: Re: md failing mechanism
Date: Sat, 23 Jan 2016 02:07:37 +0300 [thread overview]
Message-ID: <56A2B639.7000902@yandex.ru> (raw)
In-Reply-To: <CACsGCyTUBRrQgt0GiVp1R6pv-4gO44Ro7pgm4iCq+1KwWDoPsg@mail.gmail.com>
> Depending on your distribution, you may have been scrubbing all along.
> Notice that if you have problems with timeouts, then this scrubbing
> can break your array by causing you to hit a bad sector and fail as
> Phil and others have described in several of his referenced EMails.
I remember disabling scrubbing myself. My reasons were not very...
bright, but now it turned out to be a it's a good thing, because with
TL;DR disabled by default, it could lead to that kind of bad things
happening, yes. I remember having one drive kicked out of an array in my
home storage, and since then, I've learned to use write-intent bitmaps
to re-add them more easily. But I'm a BAARF person, so I only have
mirrors; I wonder what happens if the only drive in a degraded mirror
fails?..
> I took the script from this Email:
>
> https://www.marc.info/?l=linux-raid&m=144661276420400&w=2
>
> and dropped that code in my /etc/rc.d/rc.local after verifying that my
> Linux distribution still ran that script on every startup. YMMV.
> That solved my problem. Good luck.
I was afraid to learn that my latest pack of drives are modern enough to
be castrated already, but it turned out they are not. :) My anime is
safe with the last 5900RPM Hitachi drives available, and they do support
TL;DR. I wish Hitachi made more 5900RPM drives for such purposes...
--
darkpenguin
next prev parent reply other threads:[~2016-01-22 23:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 17:59 md failing mechanism Dark Penguin
2016-01-22 19:29 ` Phil Turmel
2016-01-22 20:00 ` Wols Lists
2016-01-22 21:44 ` Dark Penguin
2016-01-22 22:18 ` Phil Turmel
2016-01-22 22:50 ` Dark Penguin
2016-01-22 23:23 ` Edward Kuns
2016-01-22 23:34 ` Wols Lists
2016-01-23 0:09 ` Dark Penguin
2016-01-22 22:37 ` Edward Kuns
2016-01-22 23:07 ` Dark Penguin [this message]
2016-01-22 23:39 ` Wols Lists
2016-01-23 0:09 ` Dark Penguin
2016-01-23 0:34 ` Phil Turmel
2016-01-23 10:33 ` Dark Penguin
2016-01-23 15:12 ` Phil Turmel
2016-01-22 23:40 ` James J
2016-01-23 0:44 ` Phil Turmel
2016-01-23 14:09 ` Wols Lists
2016-01-23 19:02 ` James J
2016-01-24 22:13 ` Adam Goryachev
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=56A2B639.7000902@yandex.ru \
--to=darkpenguin@yandex.ru \
--cc=eddie.kuns@gmail.com \
--cc=linux-raid@vger.kernel.org \
/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).