All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: 4e868df3 <4e868df3@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: corrupt leaf
Date: Thu, 27 Feb 2020 01:03:14 -0700	[thread overview]
Message-ID: <CAJCQCtSxz2qxbNj8XmYmST0o=vRTNsE04VMWYTeB5T_gvnY+kg@mail.gmail.com> (raw)
In-Reply-To: <CADq=pgm7r8hNB3vVNgyvbf-M+028ENy85rkwkvab_T8sC4sJ=A@mail.gmail.com>

On Thu, Feb 27, 2020 at 12:24 AM 4e868df3 <4e868df3@gmail.com> wrote:
>
> The VM is reporting the errors.

What are the details of the storage stack? What are the Btrfs devices
backed by on the host? Physical partitions, or qcow2, or raw files? If
they are files, is chattr +C set?

And what is the cache method being used for each device?

>A power failure or crash is likely to
> blame.

The host or the VM? The VM can crash, it's fairly safe, I even use
unsafe cache on all my VMs (it's way faster) and a force power off on
VMs all the time with Btrfs and never have a problem. But, it's a
different story if the host crashes.

It's a little strange that only two devices are affected.

>Scrubs happen monthly (3 weeks ago). No other BTRFS messages in
> dmesg to report, just a bunch of sudo audit's.
>
> $ sudo btrfs scrub status /mnt/raid
> UUID:             8c1dea88-fa40-4e6e-a1a1-214ea6bcdb00
> Scrub started:    Thu Feb 27 00:16:58 2020
> Status:           aborted
> Duration:         0:02:03
> Total to scrub:   5.76TiB
> Rate:             853.91MiB/s
> Error summary:    csum=278
>   Corrected:      0
>   Uncorrectable:  278
>   Unverified:     0

Btrfs check might take a while on 5.7T. It depends on how much
metadata there is.

-- 
Chris Murphy

  reply	other threads:[~2020-02-27  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-27  5:59 corrupt leaf 4e868df3
2020-02-27  6:30 ` Chris Murphy
2020-02-27  7:23   ` 4e868df3
2020-02-27  8:03     ` Chris Murphy [this message]
2020-02-27  8:25 ` Qu Wenruo
2020-02-28  2:28   ` 4e868df3
2020-02-28  3:01     ` Qu Wenruo
2020-02-29 15:47       ` 4e868df3
2020-03-01  0:41         ` Qu Wenruo
2020-03-01  6:11           ` 4e868df3
2020-03-01 11:40             ` Qu Wenruo
2020-03-02  6:35         ` 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='CAJCQCtSxz2qxbNj8XmYmST0o=vRTNsE04VMWYTeB5T_gvnY+kg@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=4e868df3@gmail.com \
    --cc=linux-btrfs@vger.kernel.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.