From: Eric Sandeen <sandeen@sgi.com>
To: Adrian Head <ahead@bigpond.net.au>
Cc: Linux XFS Mailing List <linux-xfs@oss.sgi.com>, linux-lvm@sistina.com
Subject: [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily
Date: Fri Jan 4 13:49:02 2002 [thread overview]
Message-ID: <1010173926.1414.12.camel@stout.americas.sgi.com> (raw)
In-Reply-To: <200201020451.g024pPg00867@oss.sgi.com>
Ok, I have 2.4.17-xfs (cvs checkout today) with patches from lvm-1.0.1,
applied lvm-1.0.1-2.4.17-xfs.patch then linux-2.4.11-VFS-lock.patch.
I tried creating lvm volumes & snapshots w/ an xfs filesystem.
I did run into problems (creating snapshot against my "test" volume
while it was mounted caused an oops; creating snapshot volume then
mounting test oopsed....) but eventually I got a volume mounted, and had
a snapshot volume against it.
Overflowing the snapshot behaved well:
lvm -- giving up to snapshot /dev/test/foo on /dev/test/snap: out of
space
I'll check out the oopses to see if I can figure out what's going on.
-Eric
On Tue, 2002-01-01 at 21:51, Adrian Head wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hope everyone had a happy new year :-)
>
> I'm starting to play around with LVM with the goal of having XFS, ext3,
> reiserfs and LVM coexist nicely together.
>
> Has anyone been able to get , ext3, reiserfs, XFS and LVM running nicely
> together?
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@sgi.com SGI, Inc.
next parent reply other threads:[~2002-01-04 13:49 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 ` Eric Sandeen [this message]
2002-01-04 16:47 ` [linux-lvm] Re: Unable to get XFS, ext3, reiserfs & LVM to coexist happily Adrian Head
2002-01-04 17:37 ` Andreas Dilger
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=1010173926.1414.12.camel@stout.americas.sgi.com \
--to=sandeen@sgi.com \
--cc=ahead@bigpond.net.au \
--cc=linux-lvm@sistina.com \
--cc=linux-xfs@oss.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