linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Brian Neu <proclivity76@yahoo.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: postgresql activity causes crash, 2.6.36.1
Date: Mon, 08 Nov 2010 18:49:54 -0500	[thread overview]
Message-ID: <1289260107-sup-5774@think> (raw)
In-Reply-To: <39229.10625.qm@web51905.mail.re2.yahoo.com>

Great, this is a known bug in the O_DIRECT code.  I'll fix it up
tomorrow morning.

The problem is that we're allowing bios that are too large for btrfs to
deal with.  It doesn't show any corruption in the FS.

-chris

Excerpts from Brian Neu's message of 2010-11-08 17:50:17 -0500:
> > No, this is perfect ;) The only problem is that we're missing the  stuff
> 
> > at the very top of the oops.  That's the part that explains why  it
> > oopsed.  The stuff in this png is great, but it only shows where  it
> > oopsed.
> > 
> > -chris
> 
> 
> I changed the kernel line in grub.conf for 1280x1024, rebooted, and  
> orchestrated another crash for you.  This time I noted that db activity  was 
> necessary to cause the crash.
> 
> not my steadiest camera work, but still legible

  parent reply	other threads:[~2010-11-08 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07  1:08 postgresql activity causes crash, 2.6.36.1 Brian Neu
2010-11-08 13:58 ` Chris Mason
     [not found]   ` <303125.91065.qm@web51903.mail.re2.yahoo.com>
2010-11-08 20:37     ` Chris Mason
     [not found]       ` <39229.10625.qm@web51905.mail.re2.yahoo.com>
2010-11-08 23:49         ` Chris Mason [this message]
2010-11-11 22:05           ` Brian Neu
2010-11-11 22:07             ` Chris Mason

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=1289260107-sup-5774@think \
    --to=chris.mason@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=proclivity76@yahoo.com \
    /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).