From: Gionatan Danti <g.danti@assyoma.it>
To: Bernd Schubert <"Bernd Schubert"@fastmail.fm>
Cc: Tejun Heo <tj@kernel.org>,
Bernd Schubert <bernd.schubert@fastmail.fm>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: No I/O errors reported after SATA link hard reset
Date: Thu, 17 Aug 2017 16:23:59 +0200 [thread overview]
Message-ID: <b3f6735d333aeee62410d5cfea852fd4@assyoma.it> (raw)
In-Reply-To: <559dc5fe-c162-41e6-7f14-0f3837b64585@fastmail.fm>
Hi Bernd,
Il 17-08-2017 15:18 Bernd Schubert ha scritto:
>
> So for Gionatan the root cause was an instable power supply, but in my
> case there wasn't any power loss, there were just failed sata commands.
I tried many times to replicate the error by briefly
disconnecting/reconnecting the SATA cable, but I had *no* corruption in
this case. Sure, this was my experience, but a bad-behaving disk
firmware can do all sort of bad things with the volatile cache,
especially when renegotiating the host link.
I my case, I did *not* change the power supply, rather the SATA power
cable: my theory is that, as the previous cable was shared between the
two disks, somewhat low-voltage spiked find their ways and the second
disk simply "rebooted". The new cable is dedicated to the SATA disk wich
was previously failing.
What concern my is that, reading the linux-raid mailing list, many user
have historycally reported high mismatch count in RAID1 arrays. These
mismatches were generally discarded saying "RAID1 is prone to false
positives" but, in my experience, these "false mismatches" are quite
rare. What it means is that many users *are probably suffering* from my
(and your) problem, without never realizing that...
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2017-08-17 14:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 22:27 No I/O errors reported after SATA link hard reset Gionatan Danti
2017-08-17 9:24 ` Bernd Schubert
2017-08-17 12:48 ` Tejun Heo
2017-08-17 13:18 ` Bernd Schubert
2017-08-17 13:25 ` Tejun Heo
2017-08-17 13:43 ` Bernd Schubert
2017-08-17 14:23 ` Gionatan Danti [this message]
2017-08-17 14:15 ` Gionatan Danti
2017-08-17 14:46 ` Tejun Heo
2017-08-17 15:01 ` Gionatan Danti
-- strict thread matches above, loose matches on Subject: below --
2017-08-26 20:58 sonofagun
2017-08-27 18:42 ` Gionatan Danti
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=b3f6735d333aeee62410d5cfea852fd4@assyoma.it \
--to=g.danti@assyoma.it \
--cc="Bernd Schubert"@fastmail.fm \
--cc=bernd.schubert@fastmail.fm \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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