Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g02J62J18217 for linux-xfs-outgoing; Wed, 2 Jan 2002 11:06:02 -0800 Received: from lynx.adilger.int (h24-64-71-161.cg.shawcable.net [24.64.71.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g02J5ug18192 for ; Wed, 2 Jan 2002 11:05:56 -0800 Received: (from adilger@localhost) by lynx.adilger.int (8.11.2/8.11.2) id g02I5cU03296; Wed, 2 Jan 2002 11:05:38 -0700 Date: Wed, 2 Jan 2002 11:05:38 -0700 From: Andreas Dilger To: Adrian Head Cc: Linux XFS Mailing List , linux-lvm@sistina.com Subject: Re: [linux-lvm] Unable to get XFS, ext3, reiserfs & LVM to coexist happily Message-ID: <20020102110538.K12868@lynx.no> Mail-Followup-To: Adrian Head , Linux XFS Mailing List , linux-lvm@sistina.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from ahead@bigpond.net.au on Wed, Jan 02, 2002 at 01:51:01PM +1000 X-GPG-Key: 1024D/0D35BED6 X-GPG-Fingerprint: 7A37 5D79 BF1B CECA D44F 8A29 A488 39F5 0D35 BED6 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: O Content-Length: 1188 Lines: 34 On Jan 02, 2002 13:51 +1000, Adrian Head wrote: > > 2.4.17-xfs > + lvm-1.0.1 upgrade > (with LVM_VFS_ENHANCEMENT) > While source volume mounted: > * Can create ext3 snapshot? | Cannot test > * Can mount a ext3 snapshot? | Cannot test > * Can create resierfs snapshot? | Cannot test > undefined reference to `fsync_dev_lockfs' > undefined reference to `unlockfs' Note that you need to apply the VFS-lock patch AFTER the lvm-1.0.1 upgrade patch, otherwise that patch will reverse the VFS-lock patch! > When source & snapshot mounted: > * Cause oops when snapshot overflows? | > - ext3 | Oops > btp 5 (bdflush) You should try ext3 from 2.4.18, or get it from the ext3 CVS (at cvs.gkernel.sourceforge.net:/cvsroot/gkernel ext3). It has fixes for a number of problems caused by error conditions while running. If there is still a problem with ext3 oopsing with a full snapshot (which is essentially an oops because of an I/O error on the disk) then please file a separate bug report to the ext3 developers (ext2-devel@lists.sourceforge.net). Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/