Linux LVM users
 help / color / mirror / Atom feed
* Re: [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily]
       [not found] <20020105161447.K12868@lynx.no>
@ 2002-01-07 10:37 ` Stephen C. Tweedie
  2002-01-07 10:50   ` Steve Lord
  2002-01-15  8:23   ` Heinz J . Mauelshagen
  0 siblings, 2 replies; 3+ messages in thread
From: Stephen C. Tweedie @ 2002-01-07 10:37 UTC (permalink / raw)
  To: Adrian Head, Eric Sandeen, Linux XFS Mailing List, linux-lvm,
	ext2-devel
  Cc: Stephen Tweedie

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?

--Stephen

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily]
  2002-01-07 10:37 ` [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily] Stephen C. Tweedie
@ 2002-01-07 10:50   ` Steve Lord
  2002-01-15  8:23   ` Heinz J . Mauelshagen
  1 sibling, 0 replies; 3+ messages in thread
From: Steve Lord @ 2002-01-07 10:50 UTC (permalink / raw)
  To: Stephen C. Tweedie
  Cc: Adrian Head, Eric Sandeen, Linux XFS Mailing List, linux-lvm,
	ext2-devel

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily]
  2002-01-07 10:37 ` [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily] Stephen C. Tweedie
  2002-01-07 10:50   ` Steve Lord
@ 2002-01-15  8:23   ` Heinz J . Mauelshagen
  1 sibling, 0 replies; 3+ messages in thread
From: Heinz J . Mauelshagen @ 2002-01-15  8:23 UTC (permalink / raw)
  To: linux-lvm

On Mon, Jan 07, 2002 at 04:39:07PM +0000, 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?

LVM doesn't touch it.

> 
> --Stephen
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html

-- 

Regards,
Heinz    -- The LVM Guy --

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-01-15  8:23 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20020105161447.K12868@lynx.no>
2002-01-07 10:37 ` [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily] Stephen C. Tweedie
2002-01-07 10:50   ` Steve Lord
2002-01-15  8:23   ` Heinz J . Mauelshagen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox