From: Tomasz Chmielewski <tch@virtall.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs filesystem "hang" after page allocation failure: order:0 + kernel BUG at fs/btrfs/extent_io.c:4151
Date: Thu, 8 Aug 2013 03:02:36 +0800 [thread overview]
Message-ID: <20130808030236.6bd63d54@virtall.com> (raw)
In-Reply-To: <20130807185704.GC2397@localhost.localdomain>
On Wed, 7 Aug 2013 14:57:04 -0400
Josef Bacik <jbacik@fusionio.com> wrote:
> > One of btrfs filesystems hanged on my server.
> >
> > By "hang", I mean it's not possible to finish any write operation,
> > i.e.:
> >
> > # cd /mnt/btrfs
> >
> > # ls
> > some-file
> >
> > # touch 1
> > [it never returns to shell here]
> >
> I've just posted a patch to get rid of the panic on oom, could you
> please apply it and verify you no longer see the panic? The OOM is
> another issue, but we should at the very least not panic. Thanks,
It wasn't a panic or server hang; it was just "process hang" on uncached
read and all write operations on this particular btrfs filesystem
(there was another btrfs filesystem mounted on the same server, using
different drives / mount points, and it was still working fine).
--
Tomasz Chmielewski
http://wpkg.org
prev parent reply other threads:[~2013-08-07 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 18:17 btrfs filesystem "hang" after page allocation failure: order:0 + kernel BUG at fs/btrfs/extent_io.c:4151 Tomasz Chmielewski
2013-08-07 18:52 ` Zach Brown
2013-08-07 18:57 ` Josef Bacik
2013-08-07 19:02 ` Tomasz Chmielewski [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=20130808030236.6bd63d54@virtall.com \
--to=tch@virtall.com \
--cc=jbacik@fusionio.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.