From: Chris Murphy <lists@colorremedies.com>
To: Skibbi <skibbi@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: My first attempt to use btrfs failed miserably
Date: Mon, 3 Feb 2020 09:17:20 -0700 [thread overview]
Message-ID: <CAJCQCtRf8ZBmU=X-wRnbA=sdZ0-ynNUOAFHABCeN1WDVgPCw9Q@mail.gmail.com> (raw)
In-Reply-To: <CACN+yT-FrVi71HKANj7NRinyPoDG5Aowma9NT=UB2WGvqoLSVA@mail.gmail.com>
On Sun, Feb 2, 2020 at 11:39 PM Skibbi <skibbi@gmail.com> wrote:
>
> I removed luks encryption and had the same btrfs errors after several
> GB of writes. Then I reformatted drive to ext4 and was able to save
> 60GB without hiccups. Of course, you may be right that ext4 silently
> damages my data, but at least I was able to see it on the drive after
> remount/reboot.
It could be days or months later that it shows up as a problem, if
there's no checksumming. What version of e2fsprogs? metadata_csum
became default in e2fsprogs 1.44.0.
--
Chris Murphy
next prev parent reply other threads:[~2020-02-03 16:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 12:45 My first attempt to use btrfs failed miserably Skibbi
2020-02-02 12:56 ` Qu Wenruo
2020-02-02 13:22 ` Stephan von Krawczynski
2020-02-02 20:04 ` Chris Murphy
2020-02-02 13:29 ` Martin Raiber
2020-02-02 13:36 ` Qu Wenruo
2020-02-02 14:14 ` Roman Mamedov
2020-02-02 14:45 ` Swâmi Petaramesh
2020-02-02 23:34 ` Zygo Blaxell
2020-02-03 6:28 ` Skibbi
2020-02-03 16:12 ` Chris Murphy
2020-02-03 19:01 ` Marc Joliet
2020-02-03 7:00 ` Swâmi Petaramesh
2020-02-02 19:56 ` Chris Murphy
2020-02-03 6:38 ` Skibbi
2020-02-03 6:51 ` Qu Wenruo
2020-02-03 8:42 ` Skibbi
2020-02-03 10:10 ` Qu Wenruo
2020-02-03 10:17 ` Qu Wenruo
2020-02-03 10:56 ` Skibbi
2020-02-03 11:09 ` Qu Wenruo
2020-02-03 16:17 ` Chris Murphy [this message]
2020-02-02 19:57 ` Chris Murphy
2020-02-03 19:14 ` Achim Gratz
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='CAJCQCtRf8ZBmU=X-wRnbA=sdZ0-ynNUOAFHABCeN1WDVgPCw9Q@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=skibbi@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.