From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org, Chris Mason <clm@fb.com>,
Josef Bacik <jbacik@fb.com>, David Sterba <dsterba@suse.com>
Subject: Re: invalid files names, btrfs check can't repair it
Date: Tue, 16 Jan 2018 11:49:50 +0100 [thread overview]
Message-ID: <20180116104949.7qtf67mrdvyxrvs4@breakpoint.cc> (raw)
In-Reply-To: <4b929845-beae-9e13-2df9-ddc3232ad39a@gmx.com>
On 2018-01-16 18:22:14 [+0800], Qu Wenruo wrote:
> Btrfs check is always recommended before really mount it.
# btrfs check -p /dev/sdb4
Checking filesystem on /dev/sdb4
UUID: b3bfb56e-d445-4335-93f0-c1fb2d1f6df1
checking extents [O]
cache and super generation don't match, space cache will be invalidated
root 5 inode 57648595 errors 200, dir isize wrong
ERROR: errors found in fs roots
found 64009740288 bytes used, error(s) found
total csum bytes: 61644600
total tree bytes: 865746944
total fs tree bytes: 693469184
total extent tree bytes: 84905984
btree space waste bytes: 225096302
file data blocks allocated: 63203807232
referenced 63142268928
> However as long as there is no other problem, btrfs check should not
> report anything wrong.
Is it important to note that the filesystem is a raid1 one?
> Thanks,
> Qu
Sebastian
next prev parent reply other threads:[~2018-01-16 10:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 21:04 invalid files names, btrfs check can't repair it Sebastian Andrzej Siewior
2018-01-12 23:16 ` Timofey Titovets
2018-01-13 0:56 ` Qu Wenruo
2018-01-13 20:41 ` Sebastian Andrzej Siewior
2018-01-14 0:36 ` Qu Wenruo
2018-01-14 16:38 ` Sebastian Andrzej Siewior
2018-01-15 1:26 ` Qu Wenruo
2018-01-15 1:59 ` Lu Fengqi
2018-01-15 4:23 ` Qu Wenruo
2018-01-15 12:29 ` Sebastian Andrzej Siewior
2018-01-15 9:00 ` Sebastian Andrzej Siewior
2018-01-16 4:51 ` Qu Wenruo
2018-01-16 5:19 ` Qu Wenruo
2018-01-16 10:10 ` Sebastian Andrzej Siewior
2018-01-16 10:22 ` Qu Wenruo
2018-01-16 10:49 ` Sebastian Andrzej Siewior [this message]
2018-01-16 11:20 ` Qu Wenruo
2018-01-16 12:15 ` Sebastian Andrzej Siewior
2018-01-16 12:28 ` Qu Wenruo
2018-01-16 10:02 ` Sebastian Andrzej Siewior
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=20180116104949.7qtf67mrdvyxrvs4@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox