From: gius db <giusdbg@gmail.com>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Fwd: Fwd: [COMMAND HANGS] The command 'btrfs subvolume sync -s 2 xyz' can hangs.
Date: Mon, 7 Jan 2019 18:53:33 +0100 [thread overview]
Message-ID: <CAO6aweN5Nt3pcHarKCQOSt5U+UYB=TFamHy97kAsf3AnH3Cs0w@mail.gmail.com> (raw)
In-Reply-To: <CAO6aweMu9HUn34406Kkh-UvoDyoJH2ZdGUQx3vdx1Rj955E4KQ@mail.gmail.com>
Il giorno lun 7 gen 2019 alle ore 14:31 Qu Wenruo
<quwenruo.btrfs@gmx.com> ha scritto:
]zac[
> >> It's relatively common that extent tree get corrupted before and some
> >> unfortunately operation touching the corrupted extent tree triggered
> >> some user affecting error.
> >
> > Yes, I understand, but the use of filesytem is very specific.
> >
> > This filesystem and others that have had problems with corruption, are
> > used only as backups.
> > So the only operations that are performed are snapshot receive,
> > snapshot create, snapshot delete.
> > After the operations are finished, the filesystem is unmounted.
> >
> > It may just be a coincidence, but the problems of corruptions have
> > occurred very often after a snapshoot delete.
>
> I think this should give us a pretty good clue.
>
> Specific workload, less active usage, and normally no concurrency.
>
> And for the backup usage, you're using relatively new kernel only, right?
Yes, until a few days ago kernel 4.13.9 - 4.17.7 , now kernel 4.19.10 .
> Then this should be something taking into consideration for stress test.
]zac[
I have never been able to reproduce the condition that causes the
problem, currently I wait a few months until the problem decides to
give news of itself.
Gdb
next prev parent reply other threads:[~2019-01-07 17:53 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
[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 ` gius db [this message]
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='CAO6aweN5Nt3pcHarKCQOSt5U+UYB=TFamHy97kAsf3AnH3Cs0w@mail.gmail.com' \
--to=giusdbg@gmail.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;
as well as URLs for NNTP newsgroup(s).