From: Milan Broz <mbroz@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: Proper method of snapshotting XFS with external log using LVM2
Date: Wed, 01 Aug 2007 19:24:47 +0200 [thread overview]
Message-ID: <46B0C1DF.5070108@redhat.com> (raw)
In-Reply-To: <1185980574.2694.35.camel@server.ak.quickcircuit.co.nz>
Mario Becroft wrote:
> 2. I tried without xfs_freeze anyway just to see what would happen, and
> actually in kernel 2.6.22.1 if you simply create a snapshot of the main
> filesystem volume and destroy it several times in a row (not even
> touching the log volume yet) lvcreate hangs.
Well, probably two problems combined here.
In 2.6.22 is change in block layer which serializes generic_make_request()
calls and it causes some problems with synchronous metadata snapshot updates.
See patch which moves metadata updates to separate thread
http://www2.kernel.org/pub/linux/kernel/people/agk/patches/2.6/2.6.22/dm-snapshot-fix-invalidation-deadlock.patch
Maybe lvcreate hang is just another demonstration of this problem.
Please could you test it with 2.6.21 kernel, or with kernel with this patch applied ?
Is the bug with separate filesystem log reported in bugzilla ?
If you find problem with even patch above, please report it with
exact description how you reach this.
Milan
--
mbroz@redhat.com
prev parent reply other threads:[~2007-08-01 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 19:32 Proper method of snapshotting XFS with external log using LVM2 Mario Becroft
2007-08-01 12:17 ` David Chinner
2007-08-01 12:23 ` Mario Becroft
2007-08-01 14:09 ` David Chinner
2007-08-01 15:02 ` [linux-lvm] " Mario Becroft
2007-08-01 15:02 ` Mario Becroft
2007-08-01 17:24 ` Milan Broz [this message]
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=46B0C1DF.5070108@redhat.com \
--to=mbroz@redhat.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.