All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Xuanrui Qi <me@xuanruiqi.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Massive filesystem corruption, potentially related to eCryptfs-on-btrfs
Date: Mon, 1 Jun 2020 21:58:08 -0600	[thread overview]
Message-ID: <CAJCQCtQbORJDhYdeuhANCvk41RxeOBJjNRgh1yfa8LtuKY8iwQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR02MB4427F7962A6FD26BC147B4B2C98B0@DM6PR02MB4427.namprd02.prod.outlook.com>

On Mon, Jun 1, 2020 at 7:52 PM Xuanrui Qi <me@xuanruiqi.com> wrote:
>
> Hello Wenruo (and all),
>
> > Any log on `btrfs check` without --repair?
>
> This was all after I reformatted the partition, so it might not be as
> useful. But as you see, `dmesg` reports 14 corruption errors on
> /dev/sda1 (which has been functioning correctly) but `btrfs scrub` does
> not report any problems. I'll do a btrfs check when I boot from a live
> USB.

[    3.464079] BTRFS info (device sda1): bdev /dev/sda1 errs: wr 0, rd
0, flush 0, corrupt 14, gen 0

This is a persistent counter, not a live event. So it's probably old
if scrub isn't finding problems.


-- 
Chris Murphy

  reply	other threads:[~2020-06-02  3:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 21:08 Massive filesystem corruption, potentially related to eCryptfs-on-btrfs Xuanrui Qi
2020-06-02  1:18 ` Qu Wenruo
2020-06-02  1:51   ` Xuanrui Qi
2020-06-02  3:58     ` Chris Murphy [this message]
2020-06-02  6:04 ` Swâmi Petaramesh
2020-06-03 13:01   ` Martin Steigerwald

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=CAJCQCtQbORJDhYdeuhANCvk41RxeOBJjNRgh1yfa8LtuKY8iwQ@mail.gmail.com \
    --to=lists@colorremedies.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=me@xuanruiqi.com \
    --cc=quwenruo.btrfs@gmx.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.