From: Adrian Head <ahead@bigpond.net.au>
To: linux-lvm@sistina.com, Jeremy Hansen <jeremy@troubletext.com>
Subject: Re: [linux-lvm] summary of what I need to do to mount snapshot on XFS
Date: Wed Jan 9 17:39:01 2002 [thread overview]
Message-ID: <E16OSId-0005Vf-00@hermes.sistina.com> (raw)
In-Reply-To: <1010606990.15375.22.camel@jeremy-linux.intranet.qualys.com>
If this works for you - good. I have had heaps of issues that I have been
working with various developers and trying to get fixed.
Basically if I used the SGI 2.4.17-xfs kernel with lvm-1.0.1rc4(ish) some
file systems would work but others would fail. Some would fail on snapshot
creation, others would fail on snapshot mount and others would fail when the
snapshot overflowed. When I upgraded LVM to lvm-1.0.1 other filesystems
issues were fixed but others broke again. Check out the "Unable to get XFS,
ext3, reiserfs & LVM to coexist happily"
http://marc.theaimsgroup.com/?l=linux-lvm&m=100994364215110&w=2
thread on linux-lvm / linux-xfs mail archives and see if any of this relates
to your problem. With 2.4.17-xfs + lvm-1.0.1 upgrade patch + VFS-lock patch
ext2/3 & resierfs will operate correctly but XFS will fail at snapshot
creation. You can do a little source code change and get a XFS snapshot
created and mounted; but then it will fail on an overfull snapshot. These
problems are being worked on by myself and the great SGI XFS developers.
The lvm.c change you talk about I assume is the LVM_VFS_ENHANCEMENT change?
For some reason when adding the lvm-1.0.1 upgrade patch this disappears from
lvm.c I have been able to get this to compile with the change but I have
forgoten what I did.
This is one question I would like answered by the LVM gurus: should #define
LVM_VFS_ENHANCEMENT still be there after upgrading to lvm-1.0.1? What does
LVM_VFS_ENHANCEMENT actually do w.r.t lvm-1.0.1rc4(ish) and lvm-1.0.1? I
know that LVM_VFS_ENHANCEMENT in older LVM versions was the locking of the
VFS so that snapshots would be consistant - is this still correct and is it
still needed?
For the "large discussion" you are talking about the "Unable to get XFS,
ext3, reiserfs & LVM to coexist happily" thread - hit me off list and I will
attempt to summarise it for you.
On Thu, 10 Jan 2002 06:09, Jeremy Hansen wrote:
> My issue wasn't so much with how to create the snapshot but how to
> simultaneously mount the snapshot with the live filesystem. I saw a big
> thread about having to uncomment from lvm.c, did that but then got
> unresolved symbols...
>
> It seemed as if there were some issues and a large discussion related to
> doing this with XFS.
>
> Thanks
> -jeremy
--
Adrian Head
(Public Key available on request.)
next prev parent reply other threads:[~2002-01-09 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 9:22 [linux-lvm] summary of what I need to do to mount snapshot on XFS Jeremy Hansen
2002-01-09 6:07 ` Adrian Head
2002-01-09 7:04 ` Patrick Caulfield
2002-01-09 14:23 ` Jeremy Hansen
2002-01-09 17:39 ` Adrian Head [this message]
2002-01-15 8:19 ` Heinz J . Mauelshagen
2002-01-15 9:10 ` Adrian Head
2002-01-15 11:48 ` Andreas Dilger
2002-01-09 14:34 ` Jeremy Hansen
2002-01-10 2:40 ` Anselm Kruis
2002-01-09 14:51 ` Jeremy Hansen
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=E16OSId-0005Vf-00@hermes.sistina.com \
--to=ahead@bigpond.net.au \
--cc=jeremy@troubletext.com \
--cc=linux-lvm@sistina.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.