From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] snapshot error with xfs and disk I/O
Date: Thu, 30 Mar 2006 23:04:35 +0100 [thread overview]
Message-ID: <20060330220435.GM2690@agk.surrey.redhat.com> (raw)
In-Reply-To: <200603301009.22548.wim@unetix.nl>
On Thu, Mar 30, 2006 at 09:09:22AM +0100, Wim Bakker wrote:
> There seem to be serious problems with snapshots , lvm2 and xfs.
> As soon as there is a slight amount of disk I/O during snapshotting
> a logical volume with xfs , the following kind of kernel panic occurs:
You don't say what kernel.
Make sure it contains the dm snapshot patches from -mm (and probably
in Linus's git tree by now - I haven't checked).
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2006-03-30 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 8:09 [linux-lvm] snapshot error with xfs and disk I/O Wim Bakker
2006-03-30 22:04 ` Alasdair G Kergon [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-31 14:21 Wim Bakker
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=20060330220435.GM2690@agk.surrey.redhat.com \
--to=agk@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 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).