linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: gius db <giusdbg@gmail.com>
To: fdmanana@gmail.com
Cc: Jeff Mahoney <jeffm@suse.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [COMMAND HANGS] The command 'btrfs subvolume sync -s 2 xyz' can hangs.
Date: Tue, 8 Jan 2019 13:14:54 +0100	[thread overview]
Message-ID: <CAO6aweODMWZrsmBKvZQp0sgjQq4ZaBhJM04jEu7YpSbvvfyjDQ@mail.gmail.com> (raw)
In-Reply-To: <CAL3q7H6XWfo1HwRrV0BDVOhQJ3=8R7qd6qoZAQrTNimEYZFh8A@mail.gmail.com>

Il giorno mar 8 gen 2019 alle ore 00:11 Filipe Manana
<fdmanana@gmail.com> ha scritto:

]zac[
> > [ 1558.056931] Call Trace:
> > [ 1558.057011]  __btrfs_run_delayed_refs+0x216/0x10b0 [btrfs]
> > [ 1558.057011]  ? btrfs_free_tree_block+0x82/0x2c0 [btrfs]
> > [ 1558.057011]  btrfs_run_delayed_refs+0x78/0x180 [btrfs]
> > [ 1558.057011]  btrfs_should_end_transaction+0x3e/0x60 [btrfs]
> > [ 1558.057011]  btrfs_drop_snapshot+0x3cf/0x820 [btrfs]
> > [ 1558.057011]  ? btree_submit_bio_start+0x20/0x20 [btrfs]
> > [ 1558.057011]  btrfs_clean_one_deleted_snapshot+0xba/0xe0 [btrfs]
> > [ 1558.057011]  cleaner_kthread+0x129/0x160 [btrfs]
> > [ 1558.057011]  kthread+0x112/0x130
> > [ 1558.057011]  ? kthread_create_worker_on_cpu+0x70/0x70
> > [ 1558.057011]  ret_from_fork+0x35/0x40
> > [ 1558.057011] Code: 10 48 8b 40 50 f0 48 0f ba a8 30 23 00 00 02 0f 92 c0 41
> > 59 84 c0 0f 85 cc a4 09 00 44 89 ee 48 c7 c7 98 9e 75 c0 e8 58 33 a0 e7 <0f>
> > 0b e9 b6 a4 09 00 48 89 df e8 bf 0c ff ff 49 8b 74 24 28 4d
> > [ 1558.057011] ---[ end trace c4eefd1fdc016ceb ]---
> > [ 1558.057734] BTRFS: error (device sda3) in __btrfs_free_extent:7007:
> > errno=-2 No such entry
> > [ 1558.057742] BTRFS info (device sda3): forced readonly
> > [ 1558.057757] BTRFS: error (device sda3) in btrfs_run_delayed_refs:3076:
> > errno=-2 No such entry

> Very recently, a fix for this went into kernel 5.0-rc1:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0568e82dbe2510fc1fa664f58e5c997d3f1e649e
]zac[

Thanks for the answer.

If I understand correctly the problem is caused by the concurrence of
the cleanup process (which is started a few seconds after the end of
the snapshot deletion) with the other operations on the filesystem.

It matches what I seem to have noticed (problem that occurs after a
snapshot deletion, occurs randomly due to a race condition, etc..).

P.S. I suppose the 4.x.x kernel will not be corrected.

  reply	other threads:[~2019-01-08 12:15 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                       ` 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 [this message]
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=CAO6aweODMWZrsmBKvZQp0sgjQq4ZaBhJM04jEu7YpSbvvfyjDQ@mail.gmail.com \
    --to=giusdbg@gmail.com \
    --cc=fdmanana@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).