Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Josef Bacik <josef@redhat.com>
To: Stefan Kleijkers <stefan@unilogicnetworks.net>
Cc: Josef Bacik <josef@redhat.com>, linux-btrfs@vger.kernel.org
Subject: Re: WARNING: at fs/btrfs/inode.c:2198 btrfs_orphan_commit_root+0xa8/0xc0
Date: Thu, 1 Dec 2011 10:14:22 -0500	[thread overview]
Message-ID: <20111201151422.GA2250@localhost.localdomain> (raw)
In-Reply-To: <4ED0F44D.3070001@unilogicnetworks.net>

On Sat, Nov 26, 2011 at 03:14:37PM +0100, Stefan Kleijkers wrote:
> Hello Josef,
> 
> I've new results, is this the trace you are looking for?
> 
> Trace of OSD0: http://pastebin.com/gddLBXE4
> Dmesg of OSD0: http://pastebin.com/Uebzgkjv
> 
> OSD1 crashed a while later with the same messages.
> 

Well those look perfect, but that shouldn't be happening, essentially what that
tells me is we've somehow thought that we already have space reserved for that
inode, but we don't, and the only way we test/set that value is under a
spin_lock, so it simply cannot be happening that way.  So can you jack up your
buffer size for ftrace and re-run and get me the same info again to make sure
nothing to lost?  You can do that by doing something like this

echo 4096 > /sys/kernel/debug/traceing/buffer_size_kb

and then running the test and gather the same info as before.  Thanks,

Josef

  parent reply	other threads:[~2011-12-01 15:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 10:24 WARNING: at fs/btrfs/inode.c:2198 btrfs_orphan_commit_root+0xa8/0xc0 Stefan Kleijkers
2011-11-09 14:01 ` Christian Brunner
2011-11-09 15:35 ` Josef Bacik
2011-11-10 12:13   ` Stefan Kleijkers
2011-11-14 16:03     ` Josef Bacik
2011-11-15 19:13       ` Stefan Kleijkers
2011-11-15 19:29         ` Josef Bacik
2011-11-18 19:30           ` Stefan Kleijkers
     [not found]           ` <4EC2C940.40605@unilogicnetworks.net>
2011-11-18 19:52             ` Josef Bacik
2011-11-26 14:14               ` Stefan Kleijkers
2011-11-26 21:21                 ` Christian Brunner
2011-12-01 15:14                 ` Josef Bacik [this message]
2011-12-01 20:03                   ` Stefan Kleijkers

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=20111201151422.GA2250@localhost.localdomain \
    --to=josef@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stefan@unilogicnetworks.net \
    /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