From: Steve Feehan <sfeehan@boolecat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Help, lvm2 snapshot and XFS , using xfs_freeze to do this, but then lvcreate hang.
Date: Wed, 27 Sep 2006 09:33:28 -0400 [thread overview]
Message-ID: <20060927133328.GA30026@boolecat.com> (raw)
In-Reply-To: <451A0D03.9000204@davidb.org>
On Tue, Sep 26, 2006 at 10:32:51PM -0700, David Brown wrote:
> bowen zheng wrote:
>
> > Help, lvm2 snapshot and XFS , using xfs_freeze to do this, but then
> > lvcreate hang.
>
> The lvcreate does the xfs_freeze for you, so if you run xfs_freeze, then
> the lcreate will hang. Running it with '-u' should allow the lvcreate to
> hang.
Are you saying that the lvcreate command literally executes xfs_freeze
when used on a volume that happens to contain an XFS filesystem? Or
that creating a snapshot is equivalent to using xfs_freeze?
I too had read that it was suggested to call xfs_freeze before creating
a snapshot. This worked on a Debian system a year or two ago. And then
it stopped. I'm not sure if it was a kernel, lvm2 or xfs utilities
update that caused it to stop working. I did file a debian bug a while
back but nothing ever came of it:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=285979
> > I use lvm2 and xfs both. If I do not use xfs_freeze before, I can use
> > lvcreate snapshot the lv. And it work fine for some static files or
> > lv, but not for running system such as / (root) which will generate a
> > log of I/O error.
>
> What kind of errors are you getting. I've done this on active filesystems
> for backup purposes, and not had any problems.
Running xfsdump on the snapshot I see many warnings like:
debug: starting dump at Wed Sep 27 06:00:02 EDT 2006 ...
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692873
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692876
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692873
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692876
/sbin/xfsdump: WARNING: could not stat dirent vg0_04875.vg ino 3692872: No such file or directory
/sbin/xfsdump: WARNING: could not stat dirent vg0_04876.vg ino 3692875: No such file or directory
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692873
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692876
/sbin/xfsdump: WARNING: could not stat dirent vg0_04875.vg ino 3692872: No such file or directory: using null generation count in directory entry
/sbin/xfsdump: WARNING: could not stat dirent vg0_04876.vg ino 3692875: No such file or directory: using null generation count in directory entry
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692873
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692876
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692873
/sbin/xfsdump: WARNING: failed to get bulkstat information for inode 3692876
debug: dump complete at Wed Sep 27 06:00:04 EDT 2006 ...
--
Steve Feehan
next prev parent reply other threads:[~2006-09-27 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 5:03 [linux-lvm] Help, lvm2 snapshot and XFS , using xfs_freeze to do this, but then lvcreate hang bowen zheng
2006-09-27 5:32 ` David Brown
2006-09-27 13:33 ` Steve Feehan [this message]
2006-09-27 16:49 ` David Brown
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=20060927133328.GA30026@boolecat.com \
--to=sfeehan@boolecat.com \
--cc=linux-lvm@redhat.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.