From: Duncan <1i5t5.duncan@cox.net>
To: linux-kernel@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: btrfs: kernel BUG at mm/page-writeback.c:2286!
Date: Tue, 19 May 2015 13:00:37 +0000 (UTC) [thread overview]
Message-ID: <pan$af9b8$8bb6af9f$b6451669$1f3d25ac@cox.net> (raw)
In-Reply-To: alpine.LNX.2.03.1505191317300.21108@ws.cisco
Govindarajulu Varadarajan posted on Tue, 19 May 2015 13:25:49 +0530 as
excerpted:
> I am seeing the following crash on my btrfs filesystem with nfs export.
> If I disable the nfs share and reboot, I do not hit the crash. Look like
> the crash happens on btrfs with nfs export.
>
> Is this a known issue? Has anyone else faced this?
[Just a quick info-relay reply here; I'm not a dev and don't use nfs.
Hopefully someone with more information will reply given a few more hours
or a day or two...]
The issue has been reported by several people, now, yes. There has also
been kernel dev discussion of a problem with nfs 2.x, with a patch in
progress (don't know if it's applied yet), but it hasn't been clear, at
least to me, whether all reports correspond to that or not.
Now that you know that much, if you don't get a better reply in a day or
two, or while you are waiting, you can check the (btrfs) list archive for
more information.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-05-19 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 7:55 btrfs: kernel BUG at mm/page-writeback.c:2286! Govindarajulu Varadarajan
2015-05-19 13:00 ` Duncan [this message]
2015-05-19 13:32 ` Josef Bacik
2015-05-21 8:39 ` Govindarajulu Varadarajan
2015-05-19 13:43 ` Chris Mason
2015-05-19 13:54 ` Piotr Szymaniak
2015-05-19 14:44 ` Chris Mason
2015-05-21 8:36 ` Govindarajulu Varadarajan
2015-05-21 8:33 ` Govindarajulu Varadarajan
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='pan$af9b8$8bb6af9f$b6451669$1f3d25ac@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@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