From: "Sean Oh" <oh@linuxsecurity.co.kr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] [Q]XFS + LVM Snapshot?
Date: Sun Nov 18 00:21:02 2001 [thread overview]
Message-ID: <001601c16ff9$622f6e60$fc00a8c0@xp> (raw)
In-Reply-To: 20011117152233.R1308@lynx.no
Sorry, but where can I find that patch?
Thanks again for your reply.
----- Original Message -----
From: "Andreas Dilger" <adilger@turbolabs.com>
To: "Sean Oh" <oh@linuxsecurity.co.kr>
Cc: <linux-lvm@sistina.com>
Sent: Sunday, November 18, 2001 7:22 AM
Subject: Re: [linux-lvm] [Q]XFS + LVM Snapshot?
> On Nov 18, 2001 02:59 +0900, Sean Oh wrote:
> > Kernel: 2.4.15-pre4 with XFS patch ( linux-2.4-xfs CVS tree from SGI site)
> > LVM: current - LVM CVS
> >
> > Patches applied: linux-2.4.11-VFS-lock.patch from LVM CVS
> >
> > *I can not mount the original FS and snapshot FS at the same time. If
> > I unmount the origianal XFS FS and then mount the snapshot FS, it works,
> > tough.
>
> Yes, you need an XFS patch which does something with the filesystem UUID
> in the snapshot. XFS has a feature which prevents the same filesystem
> from being mounted more than once.
>
> What they do to fix this is to create writable snapshots. What I would
> rather they do is in the "duplicate UUID detection" code, allow mounting
> of devices which are on read-only media (e.g. a snapshot).
>
> Cheers, Andreas
> --
> Andreas Dilger
> http://sourceforge.net/projects/ext2resize/
> http://www-mddsp.enel.ucalgary.ca/People/adilger/
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
next prev parent reply other threads:[~2001-11-18 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-17 11:58 [linux-lvm] [Q]XFS + LVM Snapshot? Sean Oh
2001-11-17 16:21 ` Andreas Dilger
2001-11-18 0:21 ` Sean Oh [this message]
2001-11-19 2:30 ` Patrick Caulfield
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='001601c16ff9$622f6e60$fc00a8c0@xp' \
--to=oh@linuxsecurity.co.kr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).