All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Scott E. Blomquist" <sb@techsquare.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: "Scott E. Blomquist" <sb@techsquare.com>,
	Jojo <jojo@automatix.de>,
	linux-btrfs@vger.kernel.org
Subject: Re: btrfs hang on nfs?
Date: Tue, 15 Jan 2019 09:36:19 -0500	[thread overview]
Message-ID: <23613.61411.481078.442640@techsquare.com> (raw)
In-Reply-To: <c7b86349-4fea-e727-f912-03b5fb123ddd@suse.com>


Nikolay Borisov writes:
 > 
 <snip>
 > > 
 > > I'll have to rebuild the kernel with debug symbols.  Do I have to be
 > > booted into the kernel for that command to be useful?
 > 
 > Actually I think you are hitting the issue fixed by the following patch: 
 > https://github.com/kdave/btrfs-devel/commit/db0d10b02620b83ee592f6fc023ae146d72c5f65
 > 
 > 
 > The patch went into 4.18, yet your initial report said the hang occurs on 4.17. Could you try running 4.19 with e73e81b6d011 ("btrfs: balance dirty metadata pages in btrfs_finish_ordered_io")
 > reverted. 
 > 
 <snip>

As an update....

Yesterday after a hang up, I upgraded the firmware on the raid card.
There were items in the changelog that seemed like they might apply.

Unfortunately, later in the day the system hung up again.  It was also
unfortunate that I didn't have the debug kernel installed at the time.

I am now rebuilding a debug kernel with the patch you mention above.

FWIW i do see from fs/inode.c

        /* once for the tree */
        btrfs_put_ordered_extent(ordered_extent);

        /* Try to release some metadata so we don't get an OOM but don't wait */
        btrfs_btree_balance_dirty_nodelay(fs_info);

around the same place in the un-patched linux-4.17.14 source tree that
I built from, so I might have been hitting this in the previous kernel
also.

Cheers and thank you for all the help.

sb.  Scott Blomquist




      reply	other threads:[~2019-01-15 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-09 10:54 btrfs hang on nfs? Scott E. Blomquist
2019-01-09 12:14 ` 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 [this message]

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=23613.61411.481078.442640@techsquare.com \
    --to=sb@techsquare.com \
    --cc=jojo@automatix.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=nborisov@suse.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 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.