From: Pavel Machek <pavel@ucw.cz>
To: Sebastian Hyrwall <sh@keff.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BTRFS/EXT4 Data Corruption
Date: Thu, 2 Jul 2020 23:16:29 +0200 [thread overview]
Message-ID: <20200702211629.GA5787@amd> (raw)
In-Reply-To: <f87dcf1e-5a8a-36c2-a864-88099a66d220@keff.org>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
Hi!
> After alot of fiddling around it turned out that the problem goes away if
> doing "cp --sparse=never"
> when copying the files. This would to me exclude any hardware errors and
> feels more like something
> deeper inside the kernel.
If files contain random data, they are never sparse. It is strange
that sparse=never would make any difference.
> The box runs Kernel 3.10.105. Version >4 seems unaffected (not 100%
> confirmed, too few testboxes).
I'm afraid relevant developers will not be willing to debug 3.10
kernel.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2020-07-02 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 18:55 BTRFS/EXT4 Data Corruption Sebastian Hyrwall
2020-06-30 9:22 ` David Sterba
2020-07-02 21:16 ` Pavel Machek [this message]
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=20200702211629.GA5787@amd \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sh@keff.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 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.