I'm starting to wonder, now... I patched the kernel to increase the
stack by 100% and I still get the oops. The patch also allows me to see
stack depth, and things look ok.
FWIW, it's even simpler to show the problem, it's not necessary to
overflow the snapshot or even copy anything to them. Just create a
couple snapshot volumes, mount them, and unmount them. Unmounting the
first snapshot does a forced shutdown, unmounting the second one does a
force shutdown and then oopses.
Just for kicks I created 2 dirty xfs filesystems and mounted them
ro,norecovery, and unmounted - so at least that works.
So it looks like maybe with lvm, xfs is trying to do more log flushing
than it should on an ro filesystem, which generates the i/o error, which
shuts us down - not sure about the oops yet. I'm sure Steve will pipe
up if this theory is too far out of line. :)
On Tue, 2002-02-26 at 14:11, Steve Lord wrote:
> If it is stack overflow as we suspect then different drivers may push it
> over the edge in different ways. What we need to do is catch it in the
> act and see if there isn't something we can push off the stack.
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.