Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Cebtenzzre <cebtenzzre@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs check: root errors 400, nbytes wrong
Date: Wed, 23 Aug 2023 20:38:10 -0400	[thread overview]
Message-ID: <4a18c53b36e312b3de3296145984ed74323494ff.camel@gmail.com> (raw)

I am getting these errors from btrfs-progs v6.3.3 on Linux 6.4.7.

Can I safely run `btrfs check --repair`?

root 258 inode 123827824 errors 400, nbytes wrong
root 15685 inode 123827824 errors 400, nbytes wrong
root 15752 inode 123827824 errors 400, nbytes wrong
root 15760 inode 123827824 errors 400, nbytes wrong
root 15768 inode 123827824 errors 400, nbytes wrong
root 15772 inode 123827824 errors 400, nbytes wrong
root 15786 inode 123827824 errors 400, nbytes wrong
root 15798 inode 123827824 errors 400, nbytes wrong
root 15814 inode 123827824 errors 400, nbytes wrong
root 15818 inode 123827824 errors 400, nbytes wrong
ERROR: errors found in fs roots

Thanks,
Cebtenzzre

             reply	other threads:[~2023-08-24  0:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  0:38 Cebtenzzre [this message]
2023-08-24  5:40 ` btrfs check: root errors 400, nbytes wrong Qu Wenruo
     [not found]   ` <9d3f9b12f9512586c0bfbe42e730e4304a540127.camel@gmail.com>
2023-08-24 23:38     ` Cebtenzzre
2023-08-27  1:12   ` Cebtenzzre
2023-08-27  2:06     ` Qu Wenruo

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=4a18c53b36e312b3de3296145984ed74323494ff.camel@gmail.com \
    --to=cebtenzzre@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox