From: Andreas Dilger <adilger@turbolabs.com>
To: Adrian Head <ahead@bigpond.net.au>
Cc: Eric Sandeen <sandeen@sgi.com>,
Linux XFS Mailing List <linux-xfs@oss.sgi.com>,
linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily
Date: Fri Jan 4 17:37:01 2002 [thread overview]
Message-ID: <20020104163939.C12868@lynx.no> (raw)
In-Reply-To: <E16Md6L-0007pY-00@hermes.sistina.com>; from ahead@bigpond.net.au on Sat, Jan 05, 2002 at 08:49:22AM +1000
On Jan 05, 2002 08:49 +1000, Adrian Head wrote:
> Well this seems consistant with what I'm seeing:
> 2.4.17-xfs
> While source volume mounted:
> + lvm-1.0.1 upgrade
> + VFS-lock
> (In that order)
> * Can create ext3 snapshot? | yes
> * Can mount a ext3 snapshot? | yes
> * Can create resierfs snapshot? | yes
> * Can mount a resierfs snapshot? | yes
> * Can create xfs snapshot? | Oops
> btp 1234 (lvcreate)
> journal_start
> ext3_dirty_inode
> __mark_inode_dirty
> update_atime
> do_generic_file_read
> generic_file_read
> sys_read
> system_call
Can you repeat this test, but skip the ext3 snapshot creation part of it
entirely (i.e. create a reiserfs snapshot and an XFS snapshot, without
changing the kernel)? I'm wondering if XFS is getting an old inode that
ext3 was using, but either ext3 or XFS is not clearing it, so that is why
it is calling into ext3. Also, are you using ext3 on other filesystems in
this computer?
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-01-04 17:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201020451.g024pPg00867@oss.sgi.com>
2002-01-04 13:49 ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Eric Sandeen
2002-01-04 16:47 ` Adrian Head
2002-01-04 17:37 ` Andreas Dilger [this message]
2002-01-04 20:10 ` Adrian Head
2002-01-04 21:35 ` Adrian Head
2002-01-06 0:05 ` [linux-lvm] lvm-1.0.1rc4(ish) more robust on startup than lvm-1.0.1 Adrian Head
[not found] ` <200201050212.TAA16774@cthulhu.turbolabs.com>
2002-01-05 15:29 ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Andreas Dilger
2002-01-10 9:22 ` Adrian Head
2002-01-10 9:28 ` Patrick Caulfield
2002-01-10 15:21 ` Adrian Head
2002-01-11 2:40 ` Luca Berra
[not found] ` <200201101521.IAA17651@cthulhu.turbolabs.com>
2002-01-10 14:14 ` Andreas Dilger
2002-01-10 15:02 ` Adrian Head
[not found] ` <200201042349.g04Nnag26320@oss.sgi.com>
2002-01-04 17:12 ` Eric Sandeen
2002-01-04 20:44 ` Adrian Head
2002-01-05 17:06 ` Andreas Dilger
[not found] ` <200201050346.g053kmg29738@oss.sgi.com>
2002-01-04 21:08 ` Eric Sandeen
2002-01-07 8:05 ` Adrian Head
2002-01-07 12:58 ` Eric Sandeen
2002-01-06 0:20 ` Adrian Head
2002-01-09 16:25 ` Eric Sandeen
2002-01-09 16:40 ` Eric Sandeen
[not found] <200201071648.IAA08511@sgi.com>
2002-01-07 14:34 ` Keith Owens
[not found] <200201071508.g07F8Pg14938@oss.sgi.com>
2002-01-07 8:39 ` Keith Owens
2002-01-07 10:48 ` Adrian Head
[not found] <200201040015.RAA00441@cthulhu.turbolabs.com>
2002-01-03 18:36 ` Andreas Dilger
[not found] <6u4rm4r53e.fsf@zork.zork.net>
[not found] ` <200201031638.g03GcJg20734@oss.sgi.com>
[not found] ` <1010072497.12080.42.camel@jen.americas.sgi.com>
2002-01-03 18:13 ` Adrian Head
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=20020104163939.C12868@lynx.no \
--to=adilger@turbolabs.com \
--cc=ahead@bigpond.net.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox