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 08:58:50 -0500 [thread overview]
Message-ID: <1289224688-sup-3338@think> (raw)
In-Reply-To: <225116.26295.qm@web51906.mail.re2.yahoo.com>
Excerpts from Brian Neu's message of 2010-11-06 21:08:59 -0400:
> After a successful db startup, this crash was reproducible every time with db
> activity, or possibly just time. The filesystem is a raid1 and even after a
> reformat and restore from backup, the crash remains:
>
> Label: slash uuid: a9730db3-a475-45bb-af94-a873e235114b
> Total devices 2 FS bytes used 39.04GB
> devid 2 size 97.66GB used 48.51GB path /dev/sdb2
> devid 1 size 97.66GB used 48.53GB path /dev/sda2
>
> mounted as:
> # mount |grep sdb2
> /dev/sdb2 on / type btrfs (rw,noatime)
>
>
>
> This is transcribed from the screen, so forgive type-o's and "<blah>" . Let
> me know if I skipped something important.
Ok, could you please take a picture of the crash? We'll need all the
lines.
Which kernel are you on?
-chris
> (every line starts with [27163.079010] )
>
> Call trace:
> __btrfs_submit_bio_done+0x1b/0x1d [btrfs]
> run_one_async_done+0x94/0x98 [btrfs]
> run_ordered_completions++0x78/0xaa [btrfs]
> worker_loop+0x199/0x4ec [btrfs]
> kthread+0x0d/0xa5
> kernel_thread_helper+0x4/0x10
> ? restore_args+0x0/0x30
> ? kthread+0x0/0xa5
> ? kernel_thread_helper+0x0/0x10
> Code: 74 04 <blah blah>
> RIP [<ffff<blah> 7>] btrfs_map_bio+0x88/0x1c9
> RSP <ffb<blah>>
> ---[ end trace f8<blah> ]---
>
next prev parent reply other threads:[~2010-11-08 13:58 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 [this message]
[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
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=1289224688-sup-3338@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 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.