From: Wols Lists <antlists@youngman.org.uk>
To: "David C. Rankin" <drankinatty@suddenlinkmail.com>,
mdraid <linux-raid@vger.kernel.org>
Subject: Re: Linux 5.5 Breaks Raid1 on Device instead of Partition, Unusable I/O
Date: Thu, 5 Mar 2020 17:18:47 +0000 [thread overview]
Message-ID: <5E613477.7040208@youngman.org.uk> (raw)
In-Reply-To: <41094cf9-0e3f-e44e-7ec8-0ab433d574a1@suddenlinkmail.com>
On 04/03/20 22:53, David C. Rankin wrote:
> On 03/02/2020 12:57 AM, David C. Rankin wrote:
>> On 03/02/2020 12:51 AM, Roman Mamedov wrote:
>>> Yes, replace the drive ASAP, and see if that solves it.
>>
>> Will do, thank you!
>>
>
> Drive replaced and rebuilding:
>
> md4 : active raid1 sdc[3] sdd[2]
> 2930135488 blocks super 1.2 [2/1] [_U]
> [>....................] recovery = 1.5% (46390912/2930135488)
> finish=276.0min speed=174102K/sec
> bitmap: 1/22 pages [4KB], 65536KB chunk
>
> Things are looking good, speed=174102K/sec, which is a far-sight better than
> speed=2022K/sec. This will give a 4.5 hour rebuild (instead of a 26 day
> scrub). I suspect the virtualbox problems will disappear as well once the
> rebuild is done.
>
> Thank you to everyone for helping get me pointed in the right direction. I'll
> let you know if I have any further issues here, but I don't anticipate any
> (fingers-crossed...)
>
Raid 1 - look at dm-integrity. That should make scrubbing (hopefully)
redundant :-)
I might at last soon get my new system up and running (got a shop to
look at it - dud motherboard :-( Of course it's now out of warranty and
my supplier has gone bust, but if the shop say it was dud from the start
I might be able to claim something ...
But that means I'll have a test system - I've acquired about 6 x 1TB
drives - so I shall be playing with some slightly more heavy-duty raid
configs :-)
Cheers,
Wol
prev parent reply other threads:[~2020-03-05 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 1:50 Linux 5.5 Breaks Raid1 on Device instead of Partition, Unusable I/O David C. Rankin
2020-03-02 5:25 ` Roman Mamedov
2020-03-02 6:38 ` David C. Rankin
2020-03-02 6:46 ` David C. Rankin
2020-03-02 6:51 ` Roman Mamedov
2020-03-02 6:57 ` David C. Rankin
2020-03-02 7:08 ` Chris Murphy
2020-03-02 9:27 ` David C. Rankin
2020-03-02 11:44 ` Phil Turmel
2020-03-02 13:32 ` Wols Lists
2020-03-02 21:21 ` David C. Rankin
2020-03-02 21:09 ` Chris Murphy
2020-03-04 22:53 ` David C. Rankin
2020-03-05 17:18 ` Wols Lists [this message]
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=5E613477.7040208@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=drankinatty@suddenlinkmail.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).