From: Tejun Heo <tj@kernel.org>
To: Bernd Schubert <BerndSchubert@fastmail.fm>
Cc: Bernd Schubert <bernd.schubert@fastmail.fm>,
linux-ide@vger.kernel.org, Gionatan Danti <g.danti@assyoma.it>,
linux-scsi@vger.kernel.org
Subject: Re: No I/O errors reported after SATA link hard reset
Date: Thu, 17 Aug 2017 06:25:19 -0700 [thread overview]
Message-ID: <20170817132519.GD3238792@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <559dc5fe-c162-41e6-7f14-0f3837b64585@fastmail.fm>
Hello,
On Thu, Aug 17, 2017 at 03:18:06PM +0200, Bernd Schubert wrote:
> 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'm not sure if this was a port or cable issue - once I changed port and
> sata cable the errors disappeared. I didn't change the power supply or
> power cable. I'm now basically fighting with the data corruption that
> caused - for btrfs it at least has a checksum, but I didn't have ext4
> checksum enabled, so it is hard to figure out which files are corrupts -
> silent data corruption is not well handled by backups either.
No idea there. Retried and recovered errors shouldn't cause data
corruptions. Flaky power can behave in unexpected ways tho. What
happens if you hook up the drive on a different power supply but
revert to the port / cable which showed the problem? What does your
SMART counters say across those failures?
> Is it possible that sata eh recovery sends resets to the device, which
> makes it evict its cache?
That'd be a very broken device. It sure is theoretically possible but
I haven't seen any reports on such behaviors yet.
Thanks.
--
tejun
next prev parent reply other threads:[~2017-08-17 13:25 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 [this message]
2017-08-17 13:43 ` Bernd Schubert
2017-08-17 14:23 ` Gionatan Danti
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=20170817132519.GD3238792@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=BerndSchubert@fastmail.fm \
--cc=bernd.schubert@fastmail.fm \
--cc=g.danti@assyoma.it \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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