On Mon, 2002-01-07 at 10:39, Stephen C. Tweedie wrote: > Hi, > > On Sat, Jan 05, 2002 at 04:14:47PM -0700, Andreas Dilger wrote: > > Adrian Head <ahead@bigpond.net.au> wrote: > > > This is the full output from kdb when trying to create a snapshot on an XFS > > > volume for me. > > > > The system is running 2.4.17 + LVM patch (relatively minor) + VFS-lock > > (needed for snapshots) + 2.4.17 XFS patch, IIRC. This has been discussed > > on linux-lvm and linux-xfs for a couple of days. What is strange is that > > this is happening while doing an XFS snapshot, but the oops is consistently > > in ext3. There are several other ext3 filesystems on the system in > > question. > > Is XFS or LVM using current->journal_info for anything, and if so, is > it being left non-zero by anyone? We do not touch it, there has subsequently been a crash with ext3 removed from the kernel, so I suspect this is an XFS only issue - probably memory corruption. It appears we are doing a disk write in the unlockfs callout, possibly lvm is not in a coherent state at this point and is trampling on memory it should not be. Eric is going to remove the offending write and see if this clears it up, off the top of my head I cannot see why we need it in the unlockfs path. Steve > > --Stephen -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com
