From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Giuseppe Della Bianca <giusdbg@gmail.com>
Cc: Jeff Mahoney <jeffm@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [COMMAND HANGS] The command 'btrfs subvolume sync -s 2 xyz' can hangs.
Date: Mon, 7 Jan 2019 07:55:53 +0800 [thread overview]
Message-ID: <f441516a-7704-4e20-100f-ddd046b61be3@gmx.com> (raw)
In-Reply-To: <2025891.FNXETDMuRi@exnet.gdb.it>
[-- Attachment #1.1: Type: text/plain, Size: 1439 bytes --]
On 2019/1/7 上午1:57, Giuseppe Della Bianca wrote:
> In data domenica 6 gennaio 2019 15:12:38 CET, Qu Wenruo ha scritto:
> ]zac[
>> Do you have a full history of the kernel versions?
>
> I believe from version 4.13.9 to 4.17.7 .
> Today I updated everything to fedora 29, kernel 4.19.10 .
>
>> I'm not sure when the corruption happened.
>> It's completely possible that some old kernel caused the corruption but
>> not exposed until now.
>
> I am quite convinced that it happens during the snapshot delete and the
> subsequent cleanup.
> And maybe even the umount is part of the problem.
No, I mean the corruption which finally results the hang was there for a
long time.
It's relatively common that extent tree get corrupted before and some
unfortunately operation touching the corrupted extent tree triggered
some user affecting error.
>
>> Also, would you please run "btrfs check --readonly" on the fs?
>> It should show all corruption.
>>
>> And if "btrfs check" shows no corruption, then it's completely a bug in
>> that given kernel (and even current kernel).
>
> btrfs check reported various corruptions and fixed them.
Please paste the output if possible.
Thanks,
Qu
> A this time it seems that the filesystem works fine (it's the first time it
> does not have to be redone from scratch).
>
>> Thanks,
>> Qu
>
> No, thanks to you for your work.
>
> Gdb
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-07 0:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 15:15 [COMMAND HANGS] The command 'btrfs subvolume sync -s 2 xyz' can hangs Giuseppe Della Bianca
2018-08-09 18:48 ` Jeff Mahoney
2018-08-10 16:57 ` Giuseppe Della Bianca
2019-01-01 16:37 ` Giuseppe Della Bianca
2019-01-04 20:34 ` Jeff Mahoney
2019-01-05 12:30 ` Giuseppe Della Bianca
2019-01-06 14:12 ` Qu Wenruo
2019-01-06 17:57 ` Giuseppe Della Bianca
2019-01-06 23:55 ` Qu Wenruo [this message]
[not found] ` <CAO6awePqby834dBSgLx5r6onmD9HhGWAfN4bno0zK6pU0QjrEQ@mail.gmail.com>
2019-01-07 12:55 ` Fwd: " gius db
2019-01-07 13:31 ` Qu Wenruo
[not found] ` <CAO6aweMu9HUn34406Kkh-UvoDyoJH2ZdGUQx3vdx1Rj955E4KQ@mail.gmail.com>
2019-01-07 17:53 ` Fwd: " gius db
2019-01-07 22:40 ` Jeff Mahoney
2019-01-08 21:02 ` Giuseppe Della Bianca
2019-01-08 21:18 ` Jeff Mahoney
2019-01-08 21:55 ` Giuseppe Della Bianca
2019-01-07 23:11 ` Filipe Manana
2019-01-08 12:14 ` gius db
2019-01-08 12:29 ` Filipe Manana
2019-01-08 13:01 ` gius db
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=f441516a-7704-4e20-100f-ddd046b61be3@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=giusdbg@gmail.com \
--cc=jeffm@suse.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).