From: Eric Sandeen <sandeen@sgi.com>
To: Adrian Head <ahead@bigpond.net.au>
Cc: Linux XFS Mailing List <linux-xfs@oss.sgi.com>, linux-lvm@sistina.com
Subject: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily
Date: Fri Jan 4 17:12:01 2002 [thread overview]
Message-ID: <1010186076.1414.22.camel@stout.americas.sgi.com> (raw)
In-Reply-To: <200201042349.g04Nnag26320@oss.sgi.com>
On Fri, 2002-01-04 at 16:49, Adrian Head wrote:
> What does your backtrace look like? Its the ext3_dirt_inode in my backtrace
> thats got me. I have compiled a kernel without ext3 so will also give it a
> run later.
No, ext3 functions do not show up for me when it oopses on snapshot
creation:
kdb> bt
EBP EIP Function(args)
0xc1c2bf78 0xc013649e path_init+0x36 (0xc1c2a000)
kernel .text 0xc0100000 0xc0136468 0xc013659c
0xc1c2bf90 0xc01366cf __user_walk+0x2f (0xc1c2a000, 0x804f1bc)
kernel .text 0xc0100000 0xc01366a0 0xc01366f8
0xc1c2bfbc 0xc013381e sys_stat64+0x1a (0x8052474, 0xbfffe980, 0x40196154, 0x804f1bc, 0x3)
kernel .text 0xc0100000 0xc0133804 0xc0133874
0xc0106c5b system_call+0x33
kernel .text 0xc0100000 0xc0106c28 0xc0106c60
It's trying to stat64 /dev/sda2, one of my lvm partitions. I dunno why
this blows up. :/
The code has some fastcalls & inlines around here, though, so this may
not be the most accurate.
Still looking...
-Eric
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@sgi.com SGI, Inc.
next prev parent reply other threads:[~2002-01-04 17:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201020451.g024pPg00867@oss.sgi.com>
2002-01-04 13:49 ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Eric Sandeen
2002-01-04 16:47 ` Adrian Head
2002-01-04 17:37 ` Andreas Dilger
2002-01-04 20:10 ` Adrian Head
2002-01-04 21:35 ` Adrian Head
2002-01-06 0:05 ` [linux-lvm] lvm-1.0.1rc4(ish) more robust on startup than lvm-1.0.1 Adrian Head
[not found] ` <200201050212.TAA16774@cthulhu.turbolabs.com>
2002-01-05 15:29 ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Andreas Dilger
2002-01-10 9:22 ` Adrian Head
2002-01-10 9:28 ` Patrick Caulfield
2002-01-10 15:21 ` Adrian Head
2002-01-11 2:40 ` Luca Berra
[not found] ` <200201101521.IAA17651@cthulhu.turbolabs.com>
2002-01-10 14:14 ` Andreas Dilger
2002-01-10 15:02 ` Adrian Head
[not found] ` <200201042349.g04Nnag26320@oss.sgi.com>
2002-01-04 17:12 ` Eric Sandeen [this message]
2002-01-04 20:44 ` Adrian Head
2002-01-05 17:06 ` Andreas Dilger
[not found] ` <200201050346.g053kmg29738@oss.sgi.com>
2002-01-04 21:08 ` Eric Sandeen
2002-01-07 8:05 ` Adrian Head
2002-01-07 12:58 ` Eric Sandeen
2002-01-06 0:20 ` Adrian Head
2002-01-09 16:25 ` Eric Sandeen
2002-01-09 16:40 ` Eric Sandeen
[not found] <200201071648.IAA08511@sgi.com>
2002-01-07 14:34 ` Keith Owens
[not found] <200201071508.g07F8Pg14938@oss.sgi.com>
2002-01-07 8:39 ` Keith Owens
2002-01-07 10:48 ` Adrian Head
[not found] <200201040015.RAA00441@cthulhu.turbolabs.com>
2002-01-03 18:36 ` Andreas Dilger
[not found] <6u4rm4r53e.fsf@zork.zork.net>
[not found] ` <200201031638.g03GcJg20734@oss.sgi.com>
[not found] ` <1010072497.12080.42.camel@jen.americas.sgi.com>
2002-01-03 18:13 ` Adrian Head
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=1010186076.1414.22.camel@stout.americas.sgi.com \
--to=sandeen@sgi.com \
--cc=ahead@bigpond.net.au \
--cc=linux-lvm@sistina.com \
--cc=linux-xfs@oss.sgi.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