From: Chris Murphy <lists@colorremedies.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs check, persistent "reset isize for dir" messages
Date: Sat, 29 May 2021 15:42:08 -0600 [thread overview]
Message-ID: <CAJCQCtTTAJ6dJomJmisVJ8gzTDGbij=SVP=omn4xgVfzQvUyBQ@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtRnxq2mKOkjQzOedjnh9oxsNOFKoP92pjxDGwuUw1AOYg@mail.gmail.com>
On Thu, May 27, 2021 at 1:09 PM Chris Murphy <lists@colorremedies.com> wrote:
>
> btrfs-progs 5.11.1
>
> User is reporting many "reset isize for dir" messages with btrfs
> check, even following use of --repair. What does this message mean, is
> the file system OK, why aren't they actually being reset? Would a
> btrfs-image help?
>
> I'll ask them to retest with btrfs-progs 5.12.1 and include lowmem
> output as well as regular mode.
There are numerous other errors still with the file system, following
--repair, using btrfs-progs 5.12.1. But it looks like the "reset size
for dir" messages are gone.
btrfs image
https://cloud.mail.ru/public/Uf3R/paBECvbN2
btrfs check (redirected to file so it only contains the remaining errors)
https://bugzilla.redhat.com/attachment.cgi?id=1787825
btrfs check --mode=lowmem (also redirect to a file)
https://bugzilla.redhat.com/attachment.cgi?id=1787827
Full downstream bug report and all attachments
https://bugzilla.redhat.com/show_bug.cgi?id=1960738
--
Chris Murphy
prev parent reply other threads:[~2021-05-29 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 19:09 btrfs check, persistent "reset isize for dir" messages Chris Murphy
2021-05-29 21:42 ` Chris Murphy [this message]
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='CAJCQCtTTAJ6dJomJmisVJ8gzTDGbij=SVP=omn4xgVfzQvUyBQ@mail.gmail.com' \
--to=lists@colorremedies.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;
as well as URLs for NNTP newsgroup(s).