From: Tracy R Reed <treed@copilotconsulting.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] device-mapper ioctl cmd 2 failed: Invalid argument
Date: Wed Sep 24 08:01:02 2003 [thread overview]
Message-ID: <20030923211832.H30238@copilotconsulting.com> (raw)
In-Reply-To: <200309230924.44185.kevcorry@us.ibm.com>; from kevcorry@us.ibm.com on Tue, Sep 23, 2003 at 09:24:44AM -0500
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
On Tue, Sep 23, 2003 at 09:24:44AM -0500, Kevin Corry spake thusly:
> On Tuesday 23 September 2003 07:11, Alasdair G Kergon wrote:
> > On Sat, Sep 20, 2003 at 06:57:57PM -0700, Tracy R Reed wrote:
> > > I think I've got the latest everything:
> > > home:~# lvdisplay --version
> > > Driver version: 1.0.6
> > >
> > > I've got the latest 2.6, the latest devmapper, the latest lvm userland
> > > tools from sistina... But snaps still don't work.
> >
> > Firstly, there's some versioning mix-up here, because the driver
> > in the 2.6 kernels is not 1.0.6.
> > Secondly, snapshots are not available under 2.6 yet, though the
> > implementation work is well-advanced.
>
> Actually, if he didn't select the "ioctl interface version 4" option in the
> kernel config, it will be version 1.0.6.
Ah, I didn't notice that config option or recognize the implications of
it. No snapshots in 2.6 eh? That's unfortunate. I keep trying to find a
working configuration with which to take snapshots and keep coming up
short. I guess I'll just have to wait a while longer. Thanks for the info!
--
Tracy Reed
http://copilotconsulting.com
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
prev parent reply other threads:[~2003-09-24 8:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 15:49 [linux-lvm] device-mapper ioctl cmd 2 failed: Invalid argument Tracy R Reed
2003-09-23 7:12 ` Alasdair G Kergon
2003-09-23 12:08 ` Kevin Corry
2003-09-23 10:30 ` Joe Thornber
2003-09-23 12:08 ` Kevin Corry
2003-09-24 8:01 ` Tracy R Reed [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=20030923211832.H30238@copilotconsulting.com \
--to=treed@copilotconsulting.com \
--cc=linux-lvm@sistina.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