From: Martin Steigerwald <martin@lichtvoll.de>
To: "Sebastian Döring" <moralapostel@gmail.com>,
"Chris Murphy" <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Corruption errors on Samsung 980 Pro
Date: Tue, 17 Aug 2021 18:31:05 +0200 [thread overview]
Message-ID: <2461604.9INPc8UTF4@ananda> (raw)
In-Reply-To: <CAJCQCtROaJTj1J7t7fbX0Tjj5C7CvO=2sv02yRYHod_nQZmODQ@mail.gmail.com>
Chris Murphy - 13.08.21, 20:14:40 CEST:
> On Fri, Aug 13, 2021 at 3:50 AM Sebastian Döring
<moralapostel@gmail.com> wrote:
> > >It is BTRFS single profile on LVM on LUKS. Mount options are:
> > ...
> >
> > >I thought that a Samsung 980 Pro can easily handle "discard=async"
> > >so I>
> > used it.
> >
> > LUKS doesn't do discard unless you explicitly enable and force it.
> > Have you?
> `cryptsetup open` doesn't allow discards by default, but some distro
> installers do enable it by default. The most likely place to find out
> is looking at /etc/crypttab
It has option "discard" in there.
A few days ago BTRFS for /home had corruption errors that lead to it
being marked read only and then being unmountable until I used "btrfs
rescue zero-log". After that I was able to rsync almost all files to a
freshly created BTRFS LVM LV and recover the rest from backup. This
happened after an unintended laptop battery outage.
But I better report it in a different thread.
Best,
--
Martin
prev parent reply other threads:[~2021-08-17 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 15:05 Corruption errors on Samsung 980 Pro Martin Steigerwald
2021-07-16 15:19 ` Martin Steigerwald
2021-07-17 8:31 ` Corruption errors on Samsung 980 Pro (FIXED for now) Martin Steigerwald
2021-07-18 0:16 ` Qu Wenruo
2021-07-20 6:56 ` Martin Steigerwald
2021-07-21 15:35 ` Dennis Zhou
2021-08-12 12:44 ` Corruption errors on Samsung 980 Pro Duncan
2021-08-13 9:50 ` Sebastian Döring
2021-08-13 18:14 ` Chris Murphy
2021-08-17 16:31 ` Martin Steigerwald [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=2461604.9INPc8UTF4@ananda \
--to=martin@lichtvoll.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=moralapostel@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.