From: Christoph Hellwig <hch@infradead.org>
To: Joerg Sommrey <jo175@sommrey.de>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Oops on 2.6.9-ac16: xfs, dm and md may be involved
Date: Wed, 22 Dec 2004 18:26:06 +0000 [thread overview]
Message-ID: <20041222182606.GA14733@infradead.org> (raw)
In-Reply-To: <20041221185754.GA28356@sommrey.de>
On Tue, Dec 21, 2004 at 07:57:54PM +0100, Joerg Sommrey wrote:
> Hello,
>
> last night my box died with a kernel oops. There was a backup
> running at that time. The setup:
> - 2 SATA disks + 1 SCSI disk
> - SATA partitions build up md-raid-arrays (level 0 and 1)
> - md-raid-devices and SCSI partitions are physical volumes for dm
> - dm logical volumes are used for xfs filesystems
> - backup is done on dm-snapshots of those filesystems
Given the strange backtrace and this enormous stack of drivers I bet
you're seeing a stack overflow.
next prev parent reply other threads:[~2004-12-22 18:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 18:57 Oops on 2.6.9-ac16: xfs, dm and md may be involved Joerg Sommrey
2004-12-21 23:13 ` Nathan Scott
2004-12-22 18:26 ` Christoph Hellwig [this message]
2004-12-22 19:52 ` Joerg Sommrey
2004-12-22 23:11 ` Nathan Scott
2004-12-23 15:36 ` Joerg Sommrey
2005-01-04 22:44 ` Joerg Sommrey
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=20041222182606.GA14733@infradead.org \
--to=hch@infradead.org \
--cc=jo175@sommrey.de \
--cc=linux-kernel@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