From: Tracy R Reed <treed@copilotconsulting.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] device-mapper ioctl cmd 2 failed: Invalid argument
Date: Mon Sep 22 15:49:08 2003 [thread overview]
Message-ID: <20030920185757.A9590@copilotconsulting.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
Nobody replied to my last message about the kernel oops and I couldn't
figure it out so I thought I would try upgrading to the latest and
greatest including 2.6.0-test5. I seem to be having some sort of problem
with devmapper not communicating properly with something.
I think I've got the latest everything:
lrwxrwxrwx 1 root root 20 Sep 20 14:35
/lib/libdevmapper.so -> libdevmapper.so.1.00
home:~# lvdisplay --version
LVM version: 2.00.07 (2003-09-16)
Library version: 1.00.05-ioctl-cvs (2003-09-01)
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.
home:~# lvcreate --size 1G --snapshot --name snap /dev/system/tmp
device-mapper ioctl cmd 2 failed: Invalid argument
Couldn't load device 'system-snap'.
Problem reactivating origin tmp
Now I've got an inactive snap lv and an inactive origin lv. I can remove
the snap lv and reactivate the origin lv and everything is fine.
Any ideas what's wrong with my setup?
--
Tracy Reed
http://copilotconsulting.com
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
next reply other threads:[~2003-09-22 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 15:49 Tracy R Reed [this message]
2003-09-23 7:12 ` [linux-lvm] device-mapper ioctl cmd 2 failed: Invalid argument 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
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=20030920185757.A9590@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