From: Chris Samuel <chris@csamuel.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BUG while writing to USB btrfs filesystem
Date: Mon, 31 Jan 2011 13:57:17 +1100 [thread overview]
Message-ID: <4D46250D.2090403@csamuel.org> (raw)
In-Reply-To: <AANLkTim_+yfC4i21uu65eaEapjwdc6X2yV9bunwXezOx@mail.gmail.com>
On 31/01/11 12:33, cwillu wrote:
> [33159.490003] kernel BUG at /home/kernel-ppa/COD/linux/fs/btrfs/inode.c:1629!
It looks like this happens when btrfs_drop_extents() returns
an error, and in the code the only time that seems to happen
without already calling BUG_ON() is if it runs out of memory
at the very start:
path = btrfs_alloc_path();
if (!path)
return -ENOMEM;
Is there anything in the log from before that oops ?
NB: I just did a quick scan of btrfs_drop_extents() so it's
possible I missed something..
cheers,
Chris
--
Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC
next prev parent reply other threads:[~2011-01-31 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 22:28 BUG while writing to USB btrfs filesystem cwillu
2011-01-18 23:06 ` cwillu
2011-01-31 1:33 ` cwillu
2011-01-31 2:57 ` Chris Samuel [this message]
2011-01-31 3:11 ` cwillu
2011-01-31 3:35 ` Chris Samuel
2011-01-31 5:18 ` cwillu
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=4D46250D.2090403@csamuel.org \
--to=chris@csamuel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).