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.
