From: ein <ein.net@gmail.com>
To: Wolf <wolf@wolfsden.cz>, linux-btrfs@vger.kernel.org
Subject: Re: Scrub doesn't correct coruption
Date: Mon, 23 Oct 2017 11:29:15 +0200 [thread overview]
Message-ID: <59EDB66B.9060209@gmail.com> (raw)
In-Reply-To: <20171023083933.wlm2ar5u44yjgmuq@wolfsden.cz>
On 10/23/2017 10:39 AM, Wolf wrote:
> [...]
>
> Is this and issue somewhere inside btrfs or is disk HW related problem?
Highly unlikely hardware related. According to SMART and dmsg, there's
no indication which would suggest disk failure.
next prev parent reply other threads:[~2017-10-23 9:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 8:39 Scrub doesn't correct coruption Wolf
2017-10-23 9:17 ` Qu Wenruo
2017-10-23 9:23 ` Qu Wenruo
2017-10-23 20:18 ` Wolf
2017-10-23 9:29 ` ein [this message]
2017-10-23 20:24 ` Wolf
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=59EDB66B.9060209@gmail.com \
--to=ein.net@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wolf@wolfsden.cz \
/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