From: "David C. Rankin" <drankinatty@suddenlinkmail.com>
To: mdraid <linux-raid@vger.kernel.org>
Subject: Re: Linux 5.5 Breaks Raid1 on Device instead of Partition, Unusable I/O
Date: Mon, 2 Mar 2020 03:27:53 -0600 [thread overview]
Message-ID: <9e31d56a-a35d-2413-b6c7-4a97445d487d@suddenlinkmail.com> (raw)
In-Reply-To: <CAJCQCtTOJrvm7BnyqSSuCUa82ehZbtHgSGaQo1bzcepgdtazSw@mail.gmail.com>
On 03/02/2020 01:08 AM, Chris Murphy wrote:
> smart also reports for /de/sdc
>
> 40 53 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
>
>
> So I'm suspicious of timeout mismatch as well.
> https://raid.wiki.kernel.org/index.php/Timeout_Mismatch
>
>
> Chris Murphy
>
The strace between the virtualbox host and guess show and number of I/O waits
that would seem to fit some timeout issue like that. But according to the
page, both drives in this array provide:
SCT capabilities: (0x1085) SCT Status supported.
Which should be able to handle the correction without stumbling into the
timeout problem. Something is FUBAR. On a Archlinux guest running on that
array, At a text console when you type your user name and press [Enter], the
login may timeout before the password: prompt is ever displayed. So this is
really giving virtualbox fits.
On the host itself, you don't really notice much, other than a bit of slowdown
with readline and tab-completion every once in a while, but apps looking to
that array -- all bets are off.
And still not a single error in the journal or mailed from mdadm. You would
think if it was going to take 26 days to scrub a 3T array, some error should
pop up somewhere :-)
--
David C. Rankin, J.D.,P.E.
next prev parent reply other threads:[~2020-03-02 9:27 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 [this message]
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
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=9e31d56a-a35d-2413-b6c7-4a97445d487d@suddenlinkmail.com \
--to=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).