From: Roman Mamedov <rm@romanrm.net>
To: Timofey Titovets <nefelim4ag@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs duperemove corrupt data while dedup
Date: Thu, 27 Aug 2015 00:52:30 +0500 [thread overview]
Message-ID: <20150827005230.402ecd0d@natsu> (raw)
In-Reply-To: <CAGqmi76J4XWv+ureSG66Da_E-xq3MqGahbhsaTR6Sf2rSHd4Ug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
On Wed, 26 Aug 2015 22:33:38 +0300
Timofey Titovets <nefelim4ag@gmail.com> wrote:
> what i've got (full diff in attach):
> --- /home/nefelim4ag/dedup.after 2015-08-26 21:36:55.773452558 +0300
> +++ /home/nefelim4ag/dedup.before 2015-08-26 21:21:01.203600761 +0300
> @@ -25139,9 +25139,9 @@ caf9d41036e46b85d90a9541e8bc9ce1 /home/
> ....
> -0ccbc9c81a51f59dcf2ac0d102de37cb
> /home/nefelim4ag/L4D2/left4dead2/pak01_003.vpk
> +e665b502ee977dc1c619ecbd415c91b8
> /home/nefelim4ag/L4D2/left4dead2/pak01_000.vpk
> ....
>
> Files sizes not changed and it's > 1MB.
>
> Every time i've get a random data corruption.
I'd suggest that you use "vbindiff" to visually compare two files to check
what the actual corruption is, maybe this could give some hints. Is it the 1st
block, the last block, a few random bytes all over the place (unlikely), are
some parts zeroed out or contain just entirely different data, etc.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-08-26 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 19:33 Btrfs duperemove corrupt data while dedup Timofey Titovets
2015-08-26 19:52 ` Roman Mamedov [this message]
2015-08-26 20:00 ` Hugo Mills
2015-09-29 12:38 ` Timofey Titovets
2015-09-29 12:49 ` Filipe Manana
2015-09-29 14:53 ` Timofey Titovets
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=20150827005230.402ecd0d@natsu \
--to=rm@romanrm.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=nefelim4ag@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 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).