From: Francesco Turco <fturco@fastmail.fm>
To: Chris Murphy <lists@colorremedies.com>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Frequent btrfs corruption on a USB flash drive
Date: Thu, 7 Jul 2016 20:41:14 +0200 [thread overview]
Message-ID: <b9ae0021-baf1-454e-b87c-197726cee229@fastmail.fm> (raw)
In-Reply-To: <CAJCQCtS5wFT1q5Wrsg1ARQ0qOcmFfqG1=BdqJZ=GoZ1L+UO2AA@mail.gmail.com>
On 2016-07-07 20:25, Chris Murphy wrote:
> On Thu, Jul 7, 2016 at 8:55 AM, Francesco Turco <fturco@fastmail.fm> wrote:
>> Perhaps I
>> should try to rule out an hardware problem by filling my USB flash drive
>> with a large random file and then checking if its SHA-1 checksum
>> corresponds to the original copy on the hard disk. But first I probably
>> should backup the current Btrfs filesystem with the dd command. Can I
>> proceed?
>
> https://btrfs.wiki.kernel.org/index.php/Gotchas
Thank you for the link, I didn't know that using LVM snapshots or
mounting dd copies can create problems! That could explain the reason
for some of the problems I had in the past.
--
Website: http://www.fturco.net/
GPG key: 6712 2364 B2FE 30E1 4791 EB82 7BB1 1F53 29DE CD34
next prev parent reply other threads:[~2016-07-07 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 13:49 Frequent btrfs corruption on a USB flash drive Francesco Turco
2016-07-07 14:27 ` Austin S. Hemmelgarn
2016-07-07 14:55 ` Francesco Turco
2016-07-07 15:42 ` Austin S. Hemmelgarn
2016-07-07 18:25 ` Chris Murphy
2016-07-07 18:41 ` Francesco Turco [this message]
2016-07-07 17:57 ` Chris Murphy
2016-07-08 16:10 ` Francesco Turco
2016-07-08 16:53 ` Austin S. Hemmelgarn
2016-07-08 18:16 ` Henk Slager
2016-07-07 21:11 ` Andrew E. Mileski
2016-07-07 21:13 ` Francesco Turco
2016-07-07 22:38 ` Andrew E. Mileski
2016-07-07 23:07 ` 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=b9ae0021-baf1-454e-b87c-197726cee229@fastmail.fm \
--to=fturco@fastmail.fm \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).