From: "K. Richard Pixley" <rich@noir.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] confusing error message from lvm2
Date: Fri, 02 Apr 2010 13:29:55 -0700 [thread overview]
Message-ID: <4BB653C3.6080106@noir.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
I'm confused about an error message I'm seeing from LVM2. The message is:
+ /usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator
: -o
name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count
v4c
Path /dev/ACTION=_change_ no longer valid for device(252,7)
Path /dev/DEVTYPE=_disk_ no longer valid for device(252,7)
Path /dev/PWD=_/_ no longer valid for device(252,7)
Path /dev/DM_STATE_ACTIVE=_1_ no longer valid for device(252,7)
v4c:8.00:4.00:0.00:2047:1023:0:4:2
I'll attach a copy of a script that exhibits the problem consistently
and in only a few seconds. The script presupposes that a volume group
named "v4c" exists. Mine is 8G and is located on a physical disk.
(Well, really a vmware virtual disk, but I doubt that the kernel running
in the virtual machine really cares.)
I'm seeing this on amd64 ubuntu-9.10 updated current as of this posting.
Can anyone explain to me what this means or why I'm getting it?
--rich
[-- Attachment #2: fail.sh --]
[-- Type: text/plain, Size: 3193 bytes --]
#!/bin/sh
### This script presumes that a volume group named "v4c" exists. Mine is 8G.
set -x
/usr/bin/sudo /sbin/lvremove -f v4c
/usr/bin/sudo /sbin/lvremove -f v4c
/usr/bin/sudo /sbin/lvremove -f v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvcreate --size 1.0g --name lv-test.0 v4c
/usr/bin/sudo /sbin/mkfs -t ext4 -L lv-test.0 /dev/v4c/lv-test.0
/usr/bin/sudo /sbin/tune2fs -c 0 /dev/v4c/lv-test.0
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvcreate --snapshot --size 1.0g --name ss-test.0.0 v4c/lv-test.0
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvremove -f v4c/ss-test.0.0
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvcreate --snapshot --size 1.0g --name ss-test.0.1 v4c/lv-test.0
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvremove -f v4c/ss-test.0.1
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvremove -f v4c/lv-test.0
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvcreate --size 1.0g --name lv-test.1 v4c
/usr/bin/sudo /sbin/mkfs -t ext4 -L lv-test.1 /dev/v4c/lv-test.1
/usr/bin/sudo /sbin/tune2fs -c 0 /dev/v4c/lv-test.1
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
/usr/bin/sudo /sbin/lvs --noheadings --units g --nosuffix --separator : -o name,origin,size,snap_percent,copy_percent v4c
/usr/bin/sudo /sbin/lvcreate --snapshot --size 1.0g --name ss-test.1.0 v4c/lv-test.1
/usr/bin/sudo /sbin/vgs --noheadings --units g --nosuffix --separator : -o name,size,free,extent_size,extent_count,free_count,max_lv,lv_count,snap_count v4c
next reply other threads:[~2010-04-02 20:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 20:29 K. Richard Pixley [this message]
2010-04-03 14:29 ` [linux-lvm] confusing error message from lvm2 Alasdair G Kergon
2010-04-04 22:28 ` K. Richard Pixley
2010-04-05 11:40 ` Alasdair G Kergon
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=4BB653C3.6080106@noir.com \
--to=rich@noir.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.