From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
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 20:28:41 +0800 [thread overview]
Message-ID: <31d45254-646d-2332-d993-ca7a9d654553@gmx.com> (raw)
In-Reply-To: <20180116121553.eldnuftys54zwcuy@breakpoint.cc>
[-- Attachment #1.1: Type: text/plain, Size: 1134 bytes --]
On 2018年01月16日 20:15, Sebastian Andrzej Siewior wrote:
> On 2018-01-16 19:20:56 [+0800], Qu Wenruo wrote:
>> This is a very minor problem.
>>
>> btrfs check --repair should handle it without problem.
>
> awesome, thank you! After the --repair completed, the following didn't
> report the error anymore. And now I was able to remove the two files.
> Thank you.
And thanks for your report on this issue too, I'm working on the generic
repair function for such type mismatch and name len mismatch.
It would be soon to see such repair function in btrfs-progs, and no need
to bother using any hard coded fixer.
(Just a little spoiler, the repair functionality will land in lowmem
mode first, as lowmem mode already have such infrastructure to address
it, although if executed with mainline btrfs-progs, it will just worse
the problem)
Thanks,
Qu
>
>> Thanks,
>> Qu
>
> Sebastian
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2018-01-16 12:29 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
2018-01-16 11:20 ` Qu Wenruo
2018-01-16 12:15 ` Sebastian Andrzej Siewior
2018-01-16 12:28 ` Qu Wenruo [this message]
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=31d45254-646d-2332-d993-ca7a9d654553@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sebastian@breakpoint.cc \
/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