From: Roman Mamedov <rm@romanrm.net>
To: Martin Dev <mrturtledev@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: csum failed during copy/compare
Date: Mon, 10 Oct 2016 23:42:27 +0500 [thread overview]
Message-ID: <20161010234227.69746d3f@natsu> (raw)
In-Reply-To: <CAG6KGPSeR1zAuU0Xo9DrEpd-0QC9agB7p7z+Lb69hxS233_Cvg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On Mon, 10 Oct 2016 10:44:39 +0100
Martin Dev <mrturtledev@gmail.com> wrote:
> I work for system verification of SSDs and we've recently come up
> against an issue with BTRFS on Ubuntu 16.04
> This seems to be a recent change
...well, a change in what?
If you really didn't change anything on your machines and the used process,
there is no reason for anything to start breaking, other than obvious hardware
issues from age/etc (likely not what's happening here).
So you most likely did change something yourself, and perhaps the change was
upgrading OS version, kernel version(!!!), or versions of software in general.
As such, the first suggestion would be go through the recent software updates
history, maybe even restore an OS image you used three months ago (if
available) and confirm that the problem doesn't occur there. After that it's a
process called bisecting, there are tools for that, but likely you don't even
need those yet, just carefully note when you got which upgrades, paying
highest attention to the kernel version, and note at which point the
corruptions start to occur.
> as the same process has been used for the last 2 years
--
With respect,
Roman
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-10-10 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG6KGPS8Gvy2zGCe22mMmk4uXrqVyRP8FHayhe0ph-8vC+kA4A@mail.gmail.com>
2016-10-10 9:44 ` Fwd: csum failed during copy/compare Martin Dev
2016-10-10 12:02 ` Martin Dev
2016-10-10 13:56 ` Martin Dev
2016-10-10 18:42 ` Roman Mamedov [this message]
2016-10-10 21:05 ` Chris Murphy
2016-10-19 14:39 ` Martin Dev
2016-10-21 13:19 ` Martin Dev
2016-10-21 16:19 ` Chris Murphy
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=20161010234227.69746d3f@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=mrturtledev@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.