From: Adrian Head <ahead@bigpond.net.au>
To: "Stephenson, Dale" <dstephenson@snapserver.com>,
"'linux-xfs@oss.sgi.com'" <linux-xfs@oss.sgi.com>,
"'linux-lvm@sistina.com'" <linux-lvm@sistina.com>
Subject: [linux-lvm] Re: Oops unmounting snapshot of xfs filesystem
Date: Fri Feb 8 18:44:02 2002 [thread overview]
Message-ID: <E16ZLc9-0002WX-00@hermes.sistina.com> (raw)
In-Reply-To: <2D0AFEFEE711D611923E009027D39F2B02F08F@cdserv.meridian-data.com>
> Kernel 2.4.16 with 12/14/01 xfs CVS.
There has been heaps of work with respect to XFS and LVM since December last
year; therefore, I recommend that you try the current 2.4.17-xfs CVS. If you
don't like CVS kernels then use the split patches for 2.4.17-xfs (these
however, won't have all the latest bug fixes).
I am running 2.4.17-xfs (CVS) with LVM-1.0.2 with the xfs_fs_freeze patch and
I'm not seening your exact problem. However, there is a bug at the moment
that doesn't flush all inodes to disk on a freeze so the snapshot is not
consistant. The SGI guys are working on this at the moment.
PS. I think the xfs_fs_freeze patch is actually in the CVS now.
> LVM CVS of 1/21/02 (functionally identical to 1.0.2, I believe).
> LVM's linux-2.4.11-VFS-lock.patch.
> xfs_fs_freeze() patch posted by Eric Sandeen.
--
Adrian Head
(Public Key available on request.)
next prev parent reply other threads:[~2002-02-08 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 13:51 [linux-lvm] Oops unmounting snapshot of xfs filesystem Stephenson, Dale
2002-02-08 18:44 ` Adrian Head [this message]
2002-02-11 4:46 ` [linux-lvm] " Klaus Strebel
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 13:34 [linux-lvm] " Stephenson, Dale
2002-02-23 14:35 ` [linux-lvm] " Stephen Lord
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=E16ZLc9-0002WX-00@hermes.sistina.com \
--to=ahead@bigpond.net.au \
--cc=dstephenson@snapserver.com \
--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;
as well as URLs for NNTP newsgroup(s).