From: "Stephen C. Tweedie" <sct@redhat.com>
To: Adrian Head <ahead@bigpond.net.au>,
Eric Sandeen <sandeen@sgi.com>,
Linux XFS Mailing List <linux-xfs@oss.sgi.com>,
linux-lvm@sistina.com, ext2-devel@lists.sourceforge.net
Cc: Stephen Tweedie <sct@redhat.com>
Subject: Re: [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily]
Date: Mon Jan 7 10:37:02 2002 [thread overview]
Message-ID: <20020107163907.J20581@redhat.com> (raw)
In-Reply-To: <20020105161447.K12868@lynx.no>; from adilger@turbolabs.com on Sat, Jan 05, 2002 at 04:14:47PM -0700
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
next parent reply other threads:[~2002-01-07 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020105161447.K12868@lynx.no>
2002-01-07 10:37 ` Stephen C. Tweedie [this message]
2002-01-07 10:50 ` [Ext2-devel] [ahead@bigpond.net.au: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily] Steve Lord
2002-01-15 8:23 ` Heinz J . Mauelshagen
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=20020107163907.J20581@redhat.com \
--to=sct@redhat.com \
--cc=ahead@bigpond.net.au \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-lvm@sistina.com \
--cc=linux-xfs@oss.sgi.com \
--cc=sandeen@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.