From: Josef Bacik <josef@redhat.com>
To: Jeremy Sanders <jeremy@jeremysanders.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs hang in flush-btrfs-5
Date: Mon, 11 Jul 2011 10:30:20 -0400 [thread overview]
Message-ID: <4E1B08FC.6030907@redhat.com> (raw)
In-Reply-To: <ivenfi$iph$1@dough.gmane.org>
On 07/11/2011 07:40 AM, Jeremy Sanders wrote:
> Jeremy Sanders wrote:
>
>> Hi - I'm trying btrfs with kernel 2.6.38.8-32.fc15.x86_64 (a Fedora
>> kernel). I'm just doing a tar-to-tar copy onto the file system with
>> compress- force=zlib. Here are some traces of the stuck processes.
>
> I've managed to reproduce the hang using the latest btrfs from the
> repository. I had to remove some of the tracing lines to get it to compile
> under 2.6.38.8 and an ioctl which wasn't defined. Here is is where it is
> stuck:
>
Hrm well that is just unlikely and hard to hit. Will you try this and
see if it helps you? Thanks,
Josef
diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c
index 59cbdb1..3c8c435 100644
--- a/fs/btrfs/file.c
+++ b/fs/btrfs/file.c
@@ -1081,7 +1081,8 @@ static noinline int prepare_pages(struct
btrfs_root *root, struct file *file,
again:
for (i = 0; i < num_pages; i++) {
- pages[i] = grab_cache_page(inode->i_mapping, index + i);
+ pages[i] = find_or_create_page(inode->i_mapping, index + i,
+ GFP_NOFS);
if (!pages[i]) {
faili = i - 1;
err = -ENOMEM;
next prev parent reply other threads:[~2011-07-11 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 10:58 btrfs hang in flush-btrfs-5 Jeremy Sanders
2011-07-09 13:13 ` Jeremy Sanders
2011-07-11 11:40 ` Jeremy Sanders
2011-07-11 14:30 ` Josef Bacik [this message]
2011-07-11 21:21 ` Jeremy Sanders
2011-07-13 14:55 ` Josef Bacik
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=4E1B08FC.6030907@redhat.com \
--to=josef@redhat.com \
--cc=jeremy@jeremysanders.net \
--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.