From: Marc MERLIN <marc@merlins.org>
To: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: 4.11.3: BTRFS critical (device dm-1): unable to add free space :-17 => btrfs check --repair runs clean
Date: Tue, 20 Jun 2017 16:58:40 -0700 [thread overview]
Message-ID: <20170620235840.GC5303@merlins.org> (raw)
In-Reply-To: <20170620231202.GB5303@merlins.org>
[-- Attachment #1: Type: text/plain, Size: 4740 bytes --]
On Tue, Jun 20, 2017 at 04:12:03PM -0700, Marc MERLIN wrote:
> Given that check --repair ran clean when I ran it yesterday after this first happened,
> and I then ran mount -o clear_cache , the cache got rebuilt, and I got the problem again,
> this is not looking good, seems like a persistent bug :-/
>
> I'm now going to remount this with nospace_cache to see if your guess about
> space_cache was correct.
Now, it seems that disabling the cache is causing some serious hangs:
[ 2055.473113] INFO: task kworker/u16:17:7579 blocked for more than 120 seconds.
[ 2055.496148] Tainted: G U 4.11.6-amd64-preempt-sysrq-20170406 #6
[ 2055.520611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2055.545675] kworker/u16:17 D 0 7579 2 0x00000080
[ 2055.563626] Workqueue: writeback wb_workfn (flush-btrfs-4)
[ 2055.581458] Call Trace:
[ 2055.590154] __schedule+0x4ef/0x627
[ 2055.602830] schedule+0x89/0x9a
[ 2055.613618] io_schedule+0x16/0x38
[ 2055.625324] wait_on_page_bit_common+0xd8/0x151
[ 2055.640413] ? inode_to_bdi+0x35/0x35
[ 2055.653701] __lock_page+0x40/0x42
[ 2055.665431] lock_page+0x19/0x1c
[ 2055.676315] extent_write_cache_pages.constprop.31+0x173/0x368
[ 2055.695049] ? update_load_avg+0x227/0x3c6
[ 2055.708592] ? update_load_avg+0x3b1/0x3c6
[ 2055.722340] ? list_add+0x1a/0x34
[ 2055.733520] ? cfs_rq_throttled.isra.24+0xd/0x1d
[ 2055.748503] ? update_cfs_shares+0x2e/0xcf
[ 2055.761891] extent_writepages+0x5b/0x80
[ 2055.774854] ? __percpu_counter_compare+0x29/0x72
[ 2055.790054] ? insert_reserved_file_extent.constprop.41+0x28e/0x28e
[ 2055.809869] btrfs_writepages+0x28/0x2a
[ 2055.822516] do_writepages+0x20/0x29
[ 2055.834251] __writeback_single_inode+0x8a/0x328
[ 2055.849159] ? inode_cgwb_enabled+0xd/0x3b
[ 2055.862521] writeback_sb_inodes+0x22e/0x400
[ 2055.876310] __writeback_inodes_wb+0x6e/0xb0
[ 2055.890057] wb_writeback+0x163/0x2ca
[ 2055.902436] wb_workfn+0x1f7/0x2bf
[ 2055.913520] ? wb_workfn+0x1f7/0x2bf
[ 2055.925090] ? __switch_to+0x2c8/0x45f
[ 2055.937184] process_one_work+0x193/0x2b0
[ 2055.950034] ? rescuer_thread+0x2b1/0x2b1
[ 2055.962833] worker_thread+0x1e9/0x2c1
[ 2055.974826] ? rescuer_thread+0x2b1/0x2b1
[ 2055.988016] kthread+0xfb/0x100
[ 2055.998183] ? init_completion+0x24/0x24
[ 2056.010902] ? do_syscall_64+0x77/0x7d
[ 2056.022802] ret_from_fork+0x2c/0x40
[ 2056.034224] INFO: task rsync:27554 blocked for more than 120 seconds.
[ 2056.054213] Tainted: G U 4.11.6-amd64-preempt-sysrq-20170406 #6
[ 2056.077611] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2056.101705] rsync D 0 27554 27526 0x20020080
[ 2056.119102] Call Trace:
[ 2056.127019] __schedule+0x4ef/0x627
[ 2056.138385] schedule+0x89/0x9a
[ 2056.148616] io_schedule+0x16/0x38
[ 2056.159682] wait_on_page_bit_common+0xd8/0x151
[ 2056.173787] ? inode_to_bdi+0x35/0x35
[ 2056.185336] __lock_page+0x40/0x42
[ 2056.196176] lock_page+0x19/0x1c
[ 2056.206420] extent_write_cache_pages.constprop.31+0x173/0x368
[ 2056.224786] ? _raw_read_unlock+0xe/0x1e
[ 2056.237221] ? btrfs_set_lock_blocking_rw+0x9a/0x9d
[ 2056.252388] extent_writepages+0x5b/0x80
[ 2056.264687] ? insert_reserved_file_extent.constprop.41+0x28e/0x28e
[ 2056.284051] btrfs_writepages+0x28/0x2a
[ 2056.296117] do_writepages+0x20/0x29
[ 2056.307426] __filemap_fdatawrite_range+0x97/0xc3
[ 2056.322374] filemap_flush+0x1c/0x1e
[ 2056.333627] btrfs_rename2+0x894/0xf6f
[ 2056.345376] ? capable_wrt_inode_uidgid+0x3f/0x4e
[ 2056.359977] ? generic_permission+0x11e/0x175
[ 2056.373719] vfs_rename+0x234/0x391
[ 2056.384805] ? vfs_rename+0x234/0x391
[ 2056.396341] SYSC_renameat2+0x327/0x448
[ 2056.408349] SyS_rename+0x1e/0x20
[ 2056.418806] do_fast_syscall_32+0xb7/0xfe
[ 2056.431325] entry_SYSENTER_compat+0x4c/0x5b
[ 2056.444642] RIP: 0023:0xf76feb39
[ 2056.454861] RSP: 002b:00000000ffe177bc EFLAGS: 00000292 ORIG_RAX: 0000000000000026
[ 2056.478081] RAX: ffffffffffffffda RBX: 00000000ffe18890 RCX: 00000000ffe1a890
[ 2056.500019] RDX: 0000000000000001 RSI: 00000000ffe1a890 RDI: 0000000000000003
[ 2056.521948] RBP: 00000000ffe177f8 R08: 0000000000000000 R09: 0000000000000000
[ 2056.543858] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
[ 2056.565809] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 291 bytes --]
next prev parent reply other threads:[~2017-06-20 23:58 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 14:39 4.11.3: BTRFS critical (device dm-1): unable to add free space :-17 => btrfs check --repair runs clean Marc MERLIN
2017-06-20 15:23 ` Hugo Mills
2017-06-20 15:26 ` Marc MERLIN
2017-06-20 15:36 ` Hugo Mills
2017-06-20 15:44 ` Marc MERLIN
2017-06-20 23:12 ` Marc MERLIN
2017-06-20 23:58 ` Marc MERLIN [this message]
2017-06-21 3:31 ` Chris Murphy
2017-06-21 3:43 ` Marc MERLIN
2017-06-21 15:13 ` How to fix errors that check --mode lomem finds, but --mode normal doesn't? Marc MERLIN
2017-06-21 23:22 ` Chris Murphy
2017-06-22 0:48 ` Marc MERLIN
2017-06-22 2:22 ` Qu Wenruo
2017-06-22 2:53 ` Marc MERLIN
2017-06-22 4:08 ` Qu Wenruo
2017-06-23 4:06 ` Marc MERLIN
2017-06-23 8:54 ` Lu Fengqi
2017-06-23 16:17 ` Marc MERLIN
2017-06-24 2:34 ` Marc MERLIN
2017-06-26 10:46 ` Lu Fengqi
2017-06-27 23:11 ` Marc MERLIN
2017-06-28 7:10 ` Lu Fengqi
2017-05-01 17:06 ` 4.11 relocate crash, null pointer Marc MERLIN
2017-05-01 18:08 ` 4.11 relocate crash, null pointer + rolling back a filesystem by X hours? Marc MERLIN
2017-05-02 1:50 ` Chris Murphy
2017-05-02 3:23 ` Marc MERLIN
2017-05-02 4:56 ` Chris Murphy
2017-05-02 5:11 ` Marc MERLIN
2017-05-02 18:47 ` btrfs check --repair: failed to repair damaged filesystem, aborting Marc MERLIN
2017-05-03 6:00 ` Marc MERLIN
2017-05-03 6:17 ` Marc MERLIN
2017-05-03 6:32 ` Roman Mamedov
2017-05-03 20:40 ` Marc MERLIN
2017-07-07 5:37 ` ctree.c:197: update_ref_for_cow: BUG_ON `ret` triggered, value -5 Marc MERLIN
2017-07-07 5:39 ` Marc MERLIN
2017-07-07 9:33 ` Lu Fengqi
2017-07-07 16:38 ` Marc MERLIN
2017-07-09 4:34 ` 4.11.6 / more corruption / root 15455 has a root item with a more recent gen (33682) compared to the found root node (0) Marc MERLIN
2017-07-09 5:05 ` We really need a better/working btrfs check --repair Marc MERLIN
2017-07-09 6:34 ` 4.11.6 / more corruption / root 15455 has a root item with a more recent gen (33682) compared to the found root node (0) Marc MERLIN
2017-07-09 7:57 ` Martin Steigerwald
2017-07-09 9:16 ` Paul Jones
2017-07-09 11:17 ` Duncan
2017-07-09 13:00 ` Martin Steigerwald
2017-07-29 19:29 ` Imran Geriskovan
2017-07-29 23:38 ` Duncan
2017-07-30 14:54 ` Imran Geriskovan
2017-07-31 4:53 ` Duncan
2017-07-31 20:32 ` Imran Geriskovan
2017-08-01 1:36 ` Duncan
2017-08-01 15:18 ` Imran Geriskovan
2017-07-31 21:07 ` Ivan Sizov
2017-07-31 21:17 ` Marc MERLIN
2017-07-31 21:39 ` Ivan Sizov
2017-08-01 16:41 ` Ivan Sizov
2017-07-31 22:00 ` Justin Maggard
2017-08-01 6:38 ` Marc MERLIN
2017-05-02 19:59 ` 4.11 relocate crash, null pointer + rolling back a filesystem by X hours? Kai Krakow
2017-05-02 5:01 ` Duncan
2017-05-02 19:53 ` Kai Krakow
2017-05-23 16:58 ` Marc MERLIN
2017-05-24 10:16 ` Duncan
2017-05-05 1:19 ` Qu Wenruo
2017-05-05 2:10 ` Qu Wenruo
2017-05-05 2:40 ` Marc MERLIN
2017-05-05 5:03 ` Qu Wenruo
2017-05-05 15:43 ` Marc MERLIN
2017-05-17 18:23 ` Kai Krakow
2017-05-05 1:13 ` Qu Wenruo
2017-06-28 14:43 ` How to fix errors that check --mode lomem finds, but --mode normal doesn't? Marc MERLIN
2017-06-29 13:36 ` Lu Fengqi
2017-06-29 15:30 ` Marc MERLIN
2017-06-30 14:59 ` Lu Fengqi
2017-06-22 4:08 ` Qu Wenruo
2017-06-21 12:04 ` 4.11.3: BTRFS critical (device dm-1): unable to add free space :-17 => btrfs check --repair runs clean Duncan
2017-06-21 3:26 ` Chris Murphy
2017-06-21 4:06 ` Marc MERLIN
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=20170620235840.GC5303@merlins.org \
--to=marc@merlins.org \
--cc=hugo@carfax.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.