Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Cebtenzzre <cebtenzzre@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs check: root errors 400, nbytes wrong
Date: Thu, 24 Aug 2023 19:38:07 -0400	[thread overview]
Message-ID: <3dae04d3e9b960c06d9870db1f0b272914389d17.camel@gmail.com> (raw)
In-Reply-To: <9d3f9b12f9512586c0bfbe42e730e4304a540127.camel@gmail.com>

On Thu, 2023-08-24 at 19:32 -0400, Cebtenzzre wrote:
> On Thu, 2023-08-24 at 13:40 +0800, Qu Wenruo wrote:
> > 
> > 
> > On 2023/8/24 08:38, Cebtenzzre wrote:
> > > 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
> > 
> > Just to be extra safe, you may want to run "btrfs check --
> > mode=lowmem"
> > to get a more human readable output.
> 
> Here is the log with --mode=lowmem:
> 
> Opening filesystem to check...
> Checking filesystem on /dev/nvme0n1p2
> UUID: 76721faa-8c32-4e70-8a9e-859dece0aec1
> [1/7] checking root items
> [2/7] checking extents
> [3/7] checking free space cache
> [4/7] checking fs roots
> ERROR: root 258 INODE[123827824] nbytes 1777664 not equal to
> extent_size 1757184
> ERROR: root 259 EXTENT_DATA[1522634 4096] gap exists, expected:
> EXTENT_DATA[1522634 128]
> ERROR: root 259 EXTENT_DATA[1522636 4096] gap exists, expected:
> EXTENT_DATA[1522636 128]
> ERROR: root 407 EXTENT_DATA[398831 4096] gap exists, expected:
> EXTENT_DATA[398831 25]
> ERROR: root 407 EXTENT_DATA[398973 4096] gap exists, expected:
> EXTENT_DATA[398973 25]
> ERROR: root 407 EXTENT_DATA[398975 4096] gap exists, expected:
> EXTENT_DATA[398975 25]
> ERROR: root 407 EXTENT_DATA[398976 4096] gap exists, expected:
> EXTENT_DATA[398976 25]
> ERROR: root 407 EXTENT_DATA[418307 4096] gap exists, expected:
> EXTENT_DATA[418307 25]
> ERROR: root 407 EXTENT_DATA[418316 4096] gap exists, expected:
> EXTENT_DATA[418316 25]
> ERROR: root 407 EXTENT_DATA[418317 4096] gap exists, expected:
> EXTENT_DATA[418317 25]
> ERROR: root 407 EXTENT_DATA[420660 4096] gap exists, expected:
> EXTENT_DATA[420660 25]
> ERROR: root 407 EXTENT_DATA[420673 4096] gap exists, expected:
> EXTENT_DATA[420673 25]
> ERROR: root 407 EXTENT_DATA[439382 4096] gap exists, expected:
> EXTENT_DATA[439382 25]
> ERROR: root 407 EXTENT_DATA[439383 4096] gap exists, expected:
> EXTENT_DATA[439383 25]
> ERROR: root 407 EXTENT_DATA[451252 4096] gap exists, expected:
> EXTENT_DATA[451252 25]
> ERROR: root 407 EXTENT_DATA[451264 4096] gap exists, expected:
> EXTENT_DATA[451264 25]
> ERROR: root 407 EXTENT_DATA[451265 4096] gap exists, expected:
> EXTENT_DATA[451265 25]
> ERROR: root 407 EXTENT_DATA[452326 4096] gap exists, expected:
> EXTENT_DATA[452326 25]
> ERROR: root 407 EXTENT_DATA[452332 4096] gap exists, expected:
> EXTENT_DATA[452332 25]
> ERROR: root 407 EXTENT_DATA[452339 4096] gap exists, expected:
> EXTENT_DATA[452339 25]
> ERROR: root 407 EXTENT_DATA[4293157 4096] gap exists, expected:
> EXTENT_DATA[4293157 25]
> ERROR: root 407 EXTENT_DATA[4293570 4096] gap exists, expected:
> EXTENT_DATA[4293570 25]
> ERROR: root 407 EXTENT_DATA[4293571 4096] gap exists, expected:
> EXTENT_DATA[4293571 25]
> ERROR: root 407 EXTENT_DATA[4293572 4096] gap exists, expected:
> EXTENT_DATA[4293572 25]
> ERROR: root 407 EXTENT_DATA[4302136 4096] gap exists, expected:
> EXTENT_DATA[4302136 25]
> ERROR: root 407 EXTENT_DATA[4302148 4096] gap exists, expected:
> EXTENT_DATA[4302148 25]
> ERROR: root 407 EXTENT_DATA[4302149 4096] gap exists, expected:
> EXTENT_DATA[4302149 25]
> ERROR: root 407 EXTENT_DATA[4302150 4096] gap exists, expected:
> EXTENT_DATA[4302150 25]
> ERROR: root 407 EXTENT_DATA[5970391 4096] gap exists, expected:
> EXTENT_DATA[5970391 25]
> ERROR: root 15685 INODE[123827824] nbytes 1777664 not equal to
> extent_size 1757184
> ERROR: errors found in fs roots
> found 2324685996032 bytes used, error(s) found
> total csum bytes: 1812599528
> total tree bytes: 12918194176
> total fs tree bytes: 9882157056
> total extent tree bytes: 836272128
> btree space waste bytes: 2041051573
> file data blocks allocated: 25781547192320
>  referenced 2545608298496
> 
> Does it look okay?

Whoops, I forgot to CC the list.

> 
> > But it's mostly fine, a btrfs check --repair should be safe if and
> > only
> > if those are the only errors.
> > 
> > Thanks,
> > Qu
> > > 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


  parent reply	other threads:[~2023-08-24 23:38 UTC|newest]

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