From: "Scott E. Blomquist" <sb@techsquare.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs hang on nfs?
Date: Wed, 9 Jan 2019 05:54:57 -0500 [thread overview]
Message-ID: <23605.54017.819143.292441@techsquare.com> (raw)
Hi All,
I have a system that has been hanging/wedging frequently. It seems to
be load dependent but have not been able to isolate the problem. The
only option once the hang happens is to reboot via
/proc/sysreq_trigger
In dmesg I see this...
[Tue Jan 8 16:03:40 2019] perf: interrupt took too long (3193 > 3176), lowering kernel.perf_event_max_sample_rate to 62500
[Tue Jan 8 16:25:19 2019] perf: interrupt took too long (4013 > 3991), lowering kernel.perf_event_max_sample_rate to 49750
[Tue Jan 8 17:01:20 2019] perf: interrupt took too long (5043 > 5016), lowering kernel.perf_event_max_sample_rate to 39500
[Tue Jan 8 17:16:47 2019] INFO: task btrfs-transacti:2098 blocked for more than 120 seconds.
[Tue Jan 8 17:16:47 2019] Not tainted 4.17.14-custom #1
[Tue Jan 8 17:16:47 2019] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Tue Jan 8 17:16:47 2019] btrfs-transacti D 0 2098 2 0x80000000
[Tue Jan 8 17:16:47 2019] Call Trace:
[Tue Jan 8 17:16:47 2019] ? __schedule+0x2cf/0x850
[Tue Jan 8 17:16:47 2019] schedule+0x32/0x80
[Tue Jan 8 17:16:47 2019] btrfs_start_ordered_extent+0xca/0x100 [btrfs]
[Tue Jan 8 17:16:47 2019] ? wait_woken+0x80/0x80
[Tue Jan 8 17:16:47 2019] btrfs_wait_ordered_range+0xbd/0x110 [btrfs]
[Tue Jan 8 17:16:47 2019] __btrfs_wait_cache_io+0x49/0x1a0 [btrfs]
[Tue Jan 8 17:16:47 2019] btrfs_write_dirty_block_groups+0xed/0x360 [btrfs]
[Tue Jan 8 17:16:47 2019] ? btrfs_run_delayed_refs+0x93/0x1e0 [btrfs]
[Tue Jan 8 17:16:47 2019] commit_cowonly_roots+0x1f0/0x280 [btrfs]
[Tue Jan 8 17:16:47 2019] btrfs_commit_transaction+0x3a2/0x910 [btrfs]
[Tue Jan 8 17:16:47 2019] ? start_transaction+0x9b/0x3f0 [btrfs]
[Tue Jan 8 17:16:47 2019] transaction_kthread+0x14d/0x180 [btrfs]
[Tue Jan 8 17:16:47 2019] kthread+0xf8/0x130
[Tue Jan 8 17:16:47 2019] ? btrfs_cleanup_transaction+0x530/0x530 [btrfs]
[Tue Jan 8 17:16:47 2019] ? kthread_bind+0x10/0x10
[Tue Jan 8 17:16:47 2019] ret_from_fork+0x35/0x40
[Tue Jan 8 17:16:47 2019] INFO: task nfsd:4154 blocked for more than 120 seconds.
[Tue Jan 8 17:16:47 2019] Not tainted 4.17.14-custom #1
[Tue Jan 8 17:16:47 2019] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[Tue Jan 8 17:16:47 2019] nfsd D 0 4154 2 0x80000000
[Tue Jan 8 17:16:47 2019] Call Trace:
[Tue Jan 8 17:16:47 2019] ? __schedule+0x2cf/0x850
[Tue Jan 8 17:16:47 2019] ? iput+0x6f/0x1b0
[Tue Jan 8 17:16:47 2019] schedule+0x32/0x80
[Tue Jan 8 17:16:47 2019] rwsem_down_write_failed+0x1e0/0x350
[Tue Jan 8 17:16:47 2019] call_rwsem_down_write_failed+0x13/0x20
[Tue Jan 8 17:16:47 2019] down_write+0x29/0x40
[Tue Jan 8 17:16:47 2019] btrfs_file_write_iter+0xac/0x570 [btrfs]
[Tue Jan 8 17:16:47 2019] ? nfsd_setuser+0x103/0x270 [nfsd]
[Tue Jan 8 17:16:47 2019] do_iter_readv_writev+0xff/0x150
[Tue Jan 8 17:16:47 2019] do_iter_write+0x78/0x180
[Tue Jan 8 17:16:47 2019] nfsd_vfs_write+0xf0/0x440 [nfsd]
[Tue Jan 8 17:16:47 2019] nfsd_write+0x84/0x150 [nfsd]
[Tue Jan 8 17:16:47 2019] nfsd3_proc_write+0xcc/0x150 [nfsd]
[Tue Jan 8 17:16:47 2019] nfsd_dispatch+0xb7/0x250 [nfsd]
[Tue Jan 8 17:16:47 2019] svc_process_common+0x382/0x730 [sunrpc]
[Tue Jan 8 17:16:47 2019] svc_process+0xeb/0x100 [sunrpc]
[Tue Jan 8 17:16:47 2019] nfsd+0xe3/0x150 [nfsd]
[Tue Jan 8 17:16:47 2019] kthread+0xf8/0x130
[Tue Jan 8 17:16:47 2019] ? nfsd_destroy+0x60/0x60 [nfsd]
[Tue Jan 8 17:16:47 2019] ? kthread_bind+0x10/0x10
[Tue Jan 8 17:16:47 2019] ret_from_fork+0x35/0x40
....
here is the other relevant info...
Linux kanlabfs 4.17.14-custom #1 SMP Sun Aug 12 11:54:00 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
btrfs-progs v4.17.1
Label: '/export' uuid: 8f92c2e4-86fe-48cb-b2d3-bc36da765f02
Total devices 3 FS bytes used 75.72TiB
devid 1 size 47.30TiB used 42.22TiB path /dev/sda1
devid 2 size 21.83TiB used 16.76TiB path /dev/sdb1
devid 3 size 21.83TiB used 16.76TiB path /dev/sdc1
btrfs fi df /export/
Data, single: total=75.55TiB, used=75.54TiB
System, single: total=36.00MiB, used=7.89MiB
Metadata, single: total=187.01GiB, used=185.65GiB
GlobalReserve, single: total=512.00MiB, used=0.00B
Thanks for any help,
Cheers,
sb.
next reply other threads:[~2019-01-09 11:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 10:54 Scott E. Blomquist [this message]
2019-01-09 12:14 ` btrfs hang on nfs? Jojo
2019-01-09 13:31 ` Scott E. Blomquist
2019-01-10 11:46 ` Scott E. Blomquist
2019-01-10 11:51 ` Nikolay Borisov
2019-01-10 12:00 ` Scott E. Blomquist
2019-01-14 11:42 ` Scott E. Blomquist
2019-01-14 12:11 ` Nikolay Borisov
2019-01-14 13:13 ` Scott E. Blomquist
2019-01-14 13:28 ` Nikolay Borisov
2019-01-15 8:16 ` Nikolay Borisov
2019-01-15 14:36 ` Scott E. Blomquist
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=23605.54017.819143.292441@techsquare.com \
--to=sb@techsquare.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 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.