From: CaT <cat@zip.com.au>
To: linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: 2.6.16.20/dm: can't create more then one snapshot of an lv
Date: Tue, 27 Jun 2006 12:55:15 +1000 [thread overview]
Message-ID: <20060627025515.GC2059@zip.com.au> (raw)
In-Reply-To: <20060620142005.GA19254@agk.surrey.redhat.com>
On Tue, Jun 20, 2006 at 03:20:05PM +0100, Alasdair G Kergon wrote:
> On Mon, Jun 19, 2006 at 12:00:40PM +1000, CaT wrote:
> > I am attempting to create multiple snapshots of an lv ontop of a raid-5
> > software raid device and ext3+dir_index and resize_inode for the fs.
> > The kernel is a pure 64bit compile with Debian Sarge amd64 running on
> > top of it. The kernel is monolithic and I'm using lvm2 2.01.03-5 with
> > devmapper 1.01.
> > This works under 2.6.15.7. Under 2.6.16.20 I get this:
>
> Update to lvm2 version 2.02.01 or later and device-mapper version 1.02.02
> or later.
Done. It's all good under 2.6.16.20. Thanks for that. I'm wondering
though. I checked the minimal requirements in the
/usr/src/linux/Documentation/Changes file but nothing is mentioned for
LVM there. Is this no longer the right place to check for what userspace
utils are required for certain kernel functionality? (or was it never the
right place?)
--
"To the extent that we overreact, we proffer the terrorists the
greatest tribute."
- High Court Judge Michael Kirby
prev parent reply other threads:[~2006-06-27 2:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 2:00 2.6.16.20/dm: can't create more then one snapshot of an lv CaT
2006-06-20 0:54 ` CaT
2006-06-20 10:02 ` Heinz Mauelshagen
2006-06-20 11:46 ` CaT
2006-06-20 11:55 ` Heinz Mauelshagen
2006-06-20 12:17 ` CaT
2006-06-20 14:20 ` Alasdair G Kergon
2006-06-27 2:55 ` CaT [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=20060627025515.GC2059@zip.com.au \
--to=cat@zip.com.au \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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