From: Leslie Rhorer <lesrhorer@att.net>
To: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: My superblocks have gone missing, can't reassemble raid5
Date: Mon, 7 Jun 2021 04:52:52 -0500 [thread overview]
Message-ID: <d1da9041-9005-dc4e-2cc7-05e962bb8fcf@att.net> (raw)
In-Reply-To: <87lf89nqly.fsf@esperi.org.uk>
On 5/20/2021 2:37 PM, Nix wrote:
> On 19 May 2021, Phil Turmel spake thusly:
>
>> weekly scrubs
>
> *Weekly*? Scrubbing my arrays takes three or four days. If I ran them
> weekly the machine would never have time to do anything else!
Three or four days? How large are your arrays? I have quite a few
arrays up to 48T (64T of spindles), and none of them take more than 12
hours to scrub.
> If the storage machinery on this system is so badly off that it's
> misreading bits more often than that I think I have bigger problems.
That might be the case already.
next prev parent reply other threads:[~2021-06-07 9:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 4:16 My superblocks have gone missing, can't reassemble raid5 Christopher Thomas
2021-05-17 4:23 ` Christopher Thomas
2021-05-17 6:28 ` Roman Mamedov
2021-05-17 9:30 ` Wols Lists
[not found] ` <CAAMCDec=H=6ceP9bKjSnsQyvmZ0LqTAYzJTDmDQoBOHSJV+hDw@mail.gmail.com>
2021-05-17 13:19 ` Roman Mamedov
2021-05-18 17:47 ` Phil Turmel
2021-05-18 18:31 ` Reindl Harald
2021-05-19 13:20 ` Leslie Rhorer
2021-05-19 13:41 ` Phil Turmel
2021-05-19 16:54 ` Leslie Rhorer
2021-05-20 19:37 ` Nix
2021-06-07 9:52 ` Leslie Rhorer [this message]
2021-05-19 14:20 ` Andy Smith
2021-05-19 14:59 ` Leslie Rhorer
2021-05-19 14:48 ` Leslie Rhorer
2021-05-19 16:41 ` antlists
2021-05-19 17:03 ` Leslie Rhorer
2021-05-19 17:08 ` Leslie Rhorer
2021-05-19 18:00 ` Wols Lists
2021-05-19 19:01 ` Leslie Rhorer
2021-05-19 20:01 ` antlists
2021-05-19 23:45 ` Leslie Rhorer
2021-05-20 20:49 ` Nix
2021-05-21 4:07 ` Leslie Rhorer
2021-06-07 9:55 ` Leslie Rhorer
2021-05-20 20:48 ` Nix
2021-05-21 3:56 ` Leslie Rhorer
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=d1da9041-9005-dc4e-2cc7-05e962bb8fcf@att.net \
--to=lesrhorer@att.net \
--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