lvextend - device-mapper: create ioctl failed: Device or resource busy\nFailed to suspend
Just wondering why I can't extend a lv.
Tips on removing vg/usr would be appreciated too.
spider / # umount /backup/
spider / # lvextend -L+60G vg/backup
Extending logical volume backup to 110.00 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backup
spider / # lvchange -an vg/backup
spider / # lvextend -L+60G vg/backup
Extending logical volume backup to 110.00 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backup
spider / # lvextend -L+60G /dev/vg/backup
Extending logical volume backup to 110.00 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backup
spider / # lvs -v
Finding all logical volumes
LV VG #Seg Attr LSize Maj Min KMaj KMin Origin Snap% Move Copy% Log LV UUID
backup vg 1 -wi-a- 50.00G -1 -1 254 3 vlW378-SXL7-hdko-W6Bs-uvBt-vIRa-fEqtVE home vg 1 -wi-ao 20.00G -1 -1 254 5 qsHAy4-JbyK-ix2n-gA9h-yD4Z-kAgl-jlHXsU media vg 1 -wi-ao 50.00G -1 -1 254 6 U9C4XC-VunD-VtPP-PsJ0-YY68-2XTU-CGU2ZN tmp vg 1 -wi-ao 2.00G -1 -1 254 0 uHbozJ-j6Zv-N8dP-P8pE-tr9U-Td13-ustY6B usr1 vg 1 -wi-ao 16.08G -1 -1 254 7 EPUD1t-sJfE-2w7L-Y6Dl-EbS0-uUdr-vlisTa var vg 1 -wi-ao 10.00G -1 -1 254 2 woCb0X-lMj3-0g53-X8Sv-T1Es-4UPV-G19rDT
spider / # lvs --segments -v
Finding all logical volumes
LV VG Attr Start SSize #Str Type Stripe Chunk backup vg -wi-a- 0 50.00G 1 linear 0 0 home vg -wi-ao 0 20.00G 1 linear 0 0 media vg -wi-ao 0 50.00G 1 linear 0 0 tmp vg -wi-ao 0 2.00G 1 linear 0 0 usr1 vg -wi-ao 0 16.08G 1 linear 0 0 var vg -wi-ao 0 10.00G 1 linear 0 0
spider / # vgs -v
Finding all volume groups
Finding volume group "vg"
Archiving volume group "vg" metadata (seqno 20). Archiving volume group "vg" metadata (seqno 19). Creating volume group backup "/etc/lvm/backup/vg" (seqno 19).
VG Attr Ext #PV #LV #SN VSize VFree VG UUID
vg wz--n- 4.00M 3 6 0 253.23G 105.15G RWyOcE-8Fbs-cRWS-C4k5-Oo85-6OYt-Yf3mYN
spider / # pvs -v
Scanning for physical volume names
PV VG Fmt Attr PSize PFree DevSize PV UUID /dev/hda3 vg lvm2 a- 46.56G 46.56G 46.57G dm64JZ-JadW-gNun-oEAK-oWC6-teLP-Itd8J5 /dev/hda4 vg lvm2 a- 58.59G 42.51G 58.59G vnW9zi-bWGt-77uV-OMZA-pozZ-cZ6F-4rQwX1 /dev/hdb3 vg lvm2 a- 148.08G 16.08G 148.08G 6zSraX-fdHS-7fFx-Ji8h-mE2u-BI5F-jI9fye
spider / # dmsetup table
vg-tmp: 0 4194304 linear 3:67 94372224
vg-usr: 0 20971520 linear 3:67 384
vg-var: 0 20971520 linear 3:67 73400704
vg-backup: 0 104857600 linear 3:67 203424128
vg-opt: 0 10485760 linear 3:67 62914944
vg-home: 0 41943040 linear 3:67 20971904
vg-usr1: 0 33726464 linear 3:4 384
vg-media: 0 104857600 linear 3:67 98566528
spider / # vgdisplay
--- Volume group ---
VG Name vg
System ID
Format lvm2 Metadata Areas 3 Metadata Sequence No 19 VG Access read/write VG Status resizable MAX LV 0 Cur LV 6 Open LV 5 Max PV 0 Cur PV 3 Act PV 3 VG Size 253.23 GB PE Size 4.00 MB Total PE 64828 Alloc PE / Size 37909 / 148.08 GB Free PE / Size 26919 / 105.15 GB VG UUID RWyOcE-8Fbs-cRWS-C4k5-Oo85-6OYt-Yf3mYN
spider / # lvextend -l +15000 /dev/vg/backup
Extending logical volume backup to 108.59 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backup
spider / # lvs --version
LVM version: 2.02.02 (2006-02-07)
Library version: 1.02.03 (2006-02-08) Driver version: 4.4.0
Portage 2.0.54 (hardened/x86/2.6, gcc-3.4.5, glibc-2.3.5-r2, 2.6.14-hardened-r5 i686)
=================================================================
System uname: 2.6.14-hardened-r5 i686 Pentium III (Coppermine)
Gentoo Base System version 1.6.14
distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=pentium3 -O2 -pipe" CHOST="i686-pc-linux-gnu"
Signature · 2 lines
Daniel Black <[email protected]> Gentoo Crypto/dev-embedded/Forensics/NetMon
More info.
strace
http://dev.gentoo.org/~dragonheart/lvstrace.txt
reveils:
ioctl(9, DM_DEV_CREATE, 0x81c51c8) = -1 EBUSY
in strace when fd 9 is /dev/mapper/control
lvextend -vvvv -l +15000 /dev/vg/backup
....
... (searching other volumes)
...
#format_text/format-text.c:320 Read vg metadata (19) from /dev/hdb3 at
44032 size 2265
#metadata/pv_manip.c:241 /dev/hdb3 0: 0 2560: NULL(0:0) #metadata/pv_manip.c:241 /dev/hdb3 1: 2560 5120: home(0:0) #metadata/pv_manip.c:241 /dev/hdb3 2: 7680 1280: NULL(0:0) #metadata/pv_manip.c:241 /dev/hdb3 3: 8960 2560: var(0:0) #metadata/pv_manip.c:241 /dev/hdb3 4: 11520 512: tmp(0:0) #metadata/pv_manip.c:241 /dev/hdb3 5: 12032 12800: media(0:0) #metadata/pv_manip.c:241 /dev/hdb3 6: 24832 12800: backup(0:0) #metadata/pv_manip.c:241 /dev/hdb3 7: 37632 277: NULL(0:0) #metadata/pv_manip.c:241 /dev/hda3 0: 0 11920: NULL(0:0) #metadata/pv_manip.c:241 /dev/hda4 0: 0 4117: usr1(0:0) #metadata/pv_manip.c:241 /dev/hda4 1: 4117 10882: NULL(0:0)
#format_text/archiver.c:129 Archiving volume group "vg" metadata (seqno
19).
Extending logical volume backup to 108.59 GB
#metadata/pv_map.c:46 Allowing allocation on /dev/hdb3 start PE 0
length 2560
#metadata/pv_map.c:46 Allowing allocation on /dev/hdb3 start PE 7680
length 1280
#metadata/pv_map.c:46 Allowing allocation on /dev/hdb3 start PE 37632
length 277
#metadata/pv_map.c:46 Allowing allocation on /dev/hda3 start PE 0
length 11920
#metadata/pv_map.c:46 Allowing allocation on /dev/hda4 start PE 4117
length 10882
#metadata/pv_manip.c:241 /dev/hdb3 0: 0 2560: NULL(0:0) #metadata/pv_manip.c:241 /dev/hdb3 1: 2560 5120: home(0:0) #metadata/pv_manip.c:241 /dev/hdb3 2: 7680 1280: NULL(0:0) #metadata/pv_manip.c:241 /dev/hdb3 3: 8960 2560: var(0:0) #metadata/pv_manip.c:241 /dev/hdb3 4: 11520 512: tmp(0:0) #metadata/pv_manip.c:241 /dev/hdb3 5: 12032 12800: media(0:0) #metadata/pv_manip.c:241 /dev/hdb3 6: 24832 13077: backup(0:0) #metadata/pv_manip.c:241 /dev/hda3 0: 0 11920: backup(13077:0) #metadata/pv_manip.c:241 /dev/hda4 0: 0 4117: usr1(0:0) #metadata/pv_manip.c:241 /dev/hda4 1: 4117 2803: backup(24997:0) #metadata/pv_manip.c:241 /dev/hda4 2: 6920 8079: NULL(0:0)
#format_text/format-text.c:414 Writing vg metadata to /dev/hda3 at
17920 len 2513
#format_text/format-text.c:414 Writing vg metadata to /dev/hda4 at
17920 len 2513
#format_text/format-text.c:414 Writing vg metadata to /dev/hdb3 at
46592 len 2513
#format_text/format-text.c:516 Pre-Committing vg metadata (20)
to /dev/hda3 header at 4096
#format_text/format-text.c:516 Pre-Committing vg metadata (20)
to /dev/hda4 header at 4096
#format_text/format-text.c:516 Pre-Committing vg metadata (20)
to /dev/hdb3 header at 4096
#format_text/archiver.c:364 Creating volume group backup
"/etc/lvm/backup/vg" (seqno 20).
#format_text/format-text.c:711 Writing vg metadata
to /etc/lvm/backup/.lvm_spider_31093_1641323837
#format_text/format-text.c:755 Committing vg metadata (20)
#format_text/format-text.c:756 Renaming /etc/lvm/backup/vg.tmp
to /etc/lvm/backup/vg
#locking/file_locking.c:250 Locking LV
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE (W)
#metadata/metadata.c:1171 Finding volume group for uuid
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE
#label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected #format_text/format-text.c:320 Read vg metadata (19) from /dev/hda3 at 15360 size 2265 #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected #format_text/format-text.c:320 Read vg metadata (19) from /dev/hda4 at 15360 size 2265 #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected
#format_text/format-text.c:320 Read vg metadata (19) from /dev/hdb3 at
44032 size 2265
#metadata/metadata.c:1177 Found volume group "vg"
#metadata/metadata.c:1171 Finding volume group for uuid
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE
#label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected #format_text/format-text.c:320 Read vg pre-commit metadata (20) from /dev/hda3 at 17920 size 2513 #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected #format_text/format-text.c:320 Read vg pre-commit metadata (20) from /dev/hda4 at 17920 size 2513 #label/label.c:167 /dev/hdb3: lvm2 label detected #label/label.c:167 /dev/hda3: lvm2 label detected #label/label.c:167 /dev/hda4: lvm2 label detected
#format_text/format-text.c:320 Read vg pre-commit metadata (20)
from /dev/hdb3 at 46592 size 2513
#metadata/metadata.c:1177 Found volume group "vg"
#activate/activate.c:370 Getting device info for vg-backup
#ioctl/libdm-iface.c:1454 dm version O [16384]
#ioctl/libdm-iface.c:1454 dm info
LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE N [16384]
#ioctl/libdm-iface.c:1454 dm info
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE N [16384]
#ioctl/libdm-iface.c:1454 dm info vg-backup N [16384]
#config/config.c:757 Setting activation/missing_stripe_filler
to /dev/ioerror
#activate/dev_manager.c:588 Getting device info for vg-backup
[LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE]
#ioctl/libdm-iface.c:1454 dm info
LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE O [16384]
#ioctl/libdm-iface.c:1454 dm info
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE O [16384]
#ioctl/libdm-iface.c:1454 dm info vg-backup O [16384]
#ioctl/libdm-iface.c:1454 dm deps (254:3) O [16384]
#activate/dev_manager.c:588 Getting device info for vg-backup-real
[LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE-real]
#ioctl/libdm-iface.c:1454 dm info
LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE-real O [16384]
#ioctl/libdm-iface.c:1454 dm info
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE-real O [16384]
#ioctl/libdm-iface.c:1454 dm info vg-backup-real O [16384]
#activate/dev_manager.c:588 Getting device info for vg-backup-cow
[LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE-cow]
#ioctl/libdm-iface.c:1454 dm info
LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE-cow O [16384]
#ioctl/libdm-iface.c:1454 dm info
RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE-cow O [16384]
#ioctl/libdm-iface.c:1454 dm info vg-backup-cow O [16384]
#activate/activate.c:293 Getting target version for linear
#ioctl/libdm-iface.c:1454 dm versions O [16384]
#activate/activate.c:293 Getting target version for striped
#ioctl/libdm-iface.c:1454 dm versions O [16384]
#libdm-deptree.c:1148 Creating vg-backup
#ioctl/libdm-iface.c:1454 dm create vg-backup
LVM-RWyOcE8FbscRWSC4k5Oo856OYtYf3mYNvlW378SXL7hdkoW6BsuvBtvIRafEqtVE N [16384]
#ioctl/libdm-iface.c:1471 device-mapper: create ioctl failed: Device or
resource busy
#libdm-deptree.c:1493 <backtrace>
#activate/dev_manager.c:993 <backtrace>
#activate/activate.c:505 <backtrace>
#activate/activate.c:640 <backtrace>
#lvresize.c:530 Failed to suspend backup
#format_text/format-text.c:520 Wiping pre-committed vg metadata
from /dev/hda3 header at 4096
#format_text/format-text.c:520 Wiping pre-committed vg metadata
from /dev/hda4 header at 4096
#format_text/format-text.c:520 Wiping pre-committed vg metadata
from /dev/hdb3 header at 4096
#locking/file_locking.c:59 Unlocking /var/lock/lvm/V_vg
#device/dev-io.c:483 Closed /dev/hda3 #device/dev-io.c:483 Closed /dev/hda4 #device/dev-io.c:483 Closed /dev/hdb3
Seems to map to kernel drivers/md/dm-ioctl.c:228
Signature · 2 lines
Daniel Black <[email protected]> Gentoo Crypto/dev-embedded/Forensics/NetMon
Quoted 1 line · Daniel
spider / # umount /backup/
Shouldn't be needed. You can resize the lvol while it's mounted. Your symptoms below look like the vg metadata may be out of sync. Are you performing a pvmove or other LVM operations?
Quoted 4 lines
spider / # lvextend -L+60G vg/backup
Extending logical volume backup to 110.00 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backup
Interesting.... You gave tons of other output below, but what would be really helpful is a vgdisplay -v vg and an lvdisplay vg/backup. You also asked about removing vg/usr, however that lv only shows up in dmsetup table.
Is there a snapshot being taken? Is there an active snapshot volume? Sounds like the volume group is actually locked right now.
Signature · 3 lines
Zac Slade [email protected] ICQ:1415282 YM:krakrjak AIM:ttyp99
Quoted 4 lines · Zac Slade
Quoted 1 line · Daniel
spider / # umount /backup/
Shouldn't be needed. You can resize the lvol while it's mounted.
ok. good to know.
Quoted 2 lines
Your
symptoms below look like the vg metadata may be out of sync.
I was hoping a vgscan would reset this.
Quoted 3 lines
Are you
performing a pvmove or other LVM operations?
No other operation in progress. I dont' think i've done a pvmove either.
Quoted 7 lines
Quoted 4 lines
spider / # lvextend -L+60G vg/backup
Extending logical volume backup to 110.00 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backupInteresting.... You gave tons of other output below, but what would be really helpful is a vgdisplay -v vg and an lvdisplay vg/backup.
spider ~ # vgdisplay -v vg
Using volume group(s) on command line
Finding volume group "vg"
--- Volume group ---
VG Name vg
System ID
Format lvm2 Metadata Areas 3 Metadata Sequence No 19 VG Access read/write VG Status resizable MAX LV 0 Cur LV 6 Open LV 6 Max PV 0 Cur PV 3 Act PV 3 VG Size 253.23 GB PE Size 4.00 MB Total PE 64828 Alloc PE / Size 37909 / 148.08 GB Free PE / Size 26919 / 105.15 GB VG UUID RWyOcE-8Fbs-cRWS-C4k5-Oo85-6OYt-Yf3mYN
--- Logical volume ---
LV Name /dev/vg/home VG Name vg LV UUID qsHAy4-JbyK-ix2n-gA9h-yD4Z-kAgl-jlHXsU LV Write Access read/write LV Status available # open 1 LV Size 20.00 GB Current LE 5120 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:5
--- Logical volume ---
LV Name /dev/vg/var VG Name vg LV UUID woCb0X-lMj3-0g53-X8Sv-T1Es-4UPV-G19rDT LV Write Access read/write LV Status available # open 1 LV Size 10.00 GB Current LE 2560 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:2
--- Logical volume ---
LV Name /dev/vg/tmp VG Name vg LV UUID uHbozJ-j6Zv-N8dP-P8pE-tr9U-Td13-ustY6B LV Write Access read/write LV Status available # open 1 LV Size 2.00 GB Current LE 512 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:0
--- Logical volume ---
LV Name /dev/vg/media VG Name vg LV UUID U9C4XC-VunD-VtPP-PsJ0-YY68-2XTU-CGU2ZN LV Write Access read/write LV Status available # open 1 LV Size 50.00 GB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:6
--- Logical volume ---
LV Name /dev/vg/backup VG Name vg LV UUID vlW378-SXL7-hdko-W6Bs-uvBt-vIRa-fEqtVE LV Write Access read/write LV Status available # open 1 LV Size 50.00 GB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:3
--- Logical volume ---
LV Name /dev/vg/usr1 VG Name vg LV UUID EPUD1t-sJfE-2w7L-Y6Dl-EbS0-uUdr-vlisTa LV Write Access read/write LV Status available # open 1 LV Size 16.08 GB Current LE 4117 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:7
--- Physical volumes ---
PV Name /dev/hdb3 PV UUID 6zSraX-fdHS-7fFx-Ji8h-mE2u-BI5F-jI9fye PV Status allocatable Total PE / Free PE 37909 / 4117
PV Name /dev/hda3 PV UUID dm64JZ-JadW-gNun-oEAK-oWC6-teLP-Itd8J5 PV Status allocatable Total PE / Free PE 11920 / 11920
PV Name /dev/hda4 PV UUID vnW9zi-bWGt-77uV-OMZA-pozZ-cZ6F-4rQwX1 PV Status allocatable Total PE / Free PE 14999 / 10882
spider ~ # lvdisplay vg/backup
--- Logical volume ---
LV Name /dev/vg/backup VG Name vg LV UUID vlW378-SXL7-hdko-W6Bs-uvBt-vIRa-fEqtVE LV Write Access read/write LV Status available # open 1 LV Size 50.00 GB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:3
Quoted 3 lines
You also
asked about removing vg/usr, however that lv only shows up in dmsetup table.
I managed to remove it with a 'dmsetup remove'
Quoted 2 lines
Is there a snapshot being taken? Is there an active snapshot volume?
No. I've never played with snapshots.
Quoted 1 line
Sounds like the volume group is actually locked right now.
Anyway to reset this.? The state is persistant across reboots.
Signature · 2 lines
Daniel Black <[email protected]> Gentoo Crypto/dev-embedded/Forensics/NetMon
Guessing the additional info didn't help and there is no easy way to reset the state.
I'm going to use spare space to create a new logical volume and move data across and delete the wacky vg-backup unless any other bright ideas arise soon.
Thanks to everyone who has thought about solutions/ causes to this and offered their time to help.
Quoted 178 lines · Daniel
Quoted 4 lines · Zac Slade
Quoted 1 line · Daniel
spider / # umount /backup/
Shouldn't be needed. You can resize the lvol while it's mounted.
ok. good to know.
Quoted 2 lines
Your
symptoms below look like the vg metadata may be out of sync.I was hoping a vgscan would reset this.
Quoted 2 lines
Are you
performing a pvmove or other LVM operations?No other operation in progress. I dont' think i've done a pvmove either.
Quoted 7 lines
Quoted 4 lines
spider / # lvextend -L+60G vg/backup
Extending logical volume backup to 110.00 GB
device-mapper: create ioctl failed: Device or resource busy Failed to suspend backupInteresting.... You gave tons of other output below, but what would be really helpful is a vgdisplay -v vg and an lvdisplay vg/backup.
spider ~ # vgdisplay -v vg
Using volume group(s) on command line
Finding volume group "vg"
--- Volume group ---
VG Name vg
System IDFormat lvm2 Metadata Areas 3 Metadata Sequence No 19 VG Access read/write VG Status resizable MAX LV 0 Cur LV 6 Open LV 6 Max PV 0 Cur PV 3 Act PV 3 VG Size 253.23 GB PE Size 4.00 MB Total PE 64828 Alloc PE / Size 37909 / 148.08 GB Free PE / Size 26919 / 105.15 GB VG UUID RWyOcE-8Fbs-cRWS-C4k5-Oo85-6OYt-Yf3mYN--- Logical volume ---
LV Name /dev/vg/home VG Name vg LV UUID qsHAy4-JbyK-ix2n-gA9h-yD4Z-kAgl-jlHXsU LV Write Access read/write LV Status available # open 1 LV Size 20.00 GB Current LE 5120 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:5--- Logical volume ---
LV Name /dev/vg/var VG Name vg LV UUID woCb0X-lMj3-0g53-X8Sv-T1Es-4UPV-G19rDT LV Write Access read/write LV Status available # open 1 LV Size 10.00 GB Current LE 2560 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:2--- Logical volume ---
LV Name /dev/vg/tmp VG Name vg LV UUID uHbozJ-j6Zv-N8dP-P8pE-tr9U-Td13-ustY6B LV Write Access read/write LV Status available # open 1 LV Size 2.00 GB Current LE 512 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:0--- Logical volume ---
LV Name /dev/vg/media VG Name vg LV UUID U9C4XC-VunD-VtPP-PsJ0-YY68-2XTU-CGU2ZN LV Write Access read/write LV Status available # open 1 LV Size 50.00 GB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:6--- Logical volume ---
LV Name /dev/vg/backup VG Name vg LV UUID vlW378-SXL7-hdko-W6Bs-uvBt-vIRa-fEqtVE LV Write Access read/write LV Status available # open 1 LV Size 50.00 GB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:3--- Logical volume ---
LV Name /dev/vg/usr1 VG Name vg LV UUID EPUD1t-sJfE-2w7L-Y6Dl-EbS0-uUdr-vlisTa LV Write Access read/write LV Status available # open 1 LV Size 16.08 GB Current LE 4117 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:7--- Physical volumes ---
PV Name /dev/hdb3 PV UUID 6zSraX-fdHS-7fFx-Ji8h-mE2u-BI5F-jI9fye PV Status allocatable Total PE / Free PE 37909 / 4117PV Name /dev/hda3 PV UUID dm64JZ-JadW-gNun-oEAK-oWC6-teLP-Itd8J5 PV Status allocatable Total PE / Free PE 11920 / 11920PV Name /dev/hda4 PV UUID vnW9zi-bWGt-77uV-OMZA-pozZ-cZ6F-4rQwX1 PV Status allocatable Total PE / Free PE 14999 / 10882spider ~ # lvdisplay vg/backup
--- Logical volume ---LV Name /dev/vg/backup VG Name vg LV UUID vlW378-SXL7-hdko-W6Bs-uvBt-vIRa-fEqtVE LV Write Access read/write LV Status available # open 1 LV Size 50.00 GB Current LE 12800 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:3Quoted 3 lines
You also
asked about removing vg/usr, however that lv only shows up in dmsetup table.I managed to remove it with a 'dmsetup remove'
Quoted 1 line
Is there a snapshot being taken? Is there an active snapshot volume?
No. I've never played with snapshots.
Quoted 1 line
Sounds like the volume group is actually locked right now.
Anyway to reset this.? The state is persistant across reboots.
Signature · 2 lines
Daniel Black <[email protected]> Gentoo Crypto/dev-embedded/Forensics/NetMon
Quoted 2 lines · Daniel
Guessing the additional info didn't help and there is no easy way to reset the state.
Not really unfortunately. I have been thinking about this a lot though. I've never seen it and I'm not sure what the next move really is. Someone did suggest (and sorry for not posting sooner) that you should run lsof against /dev/mapper/control and see if something is keeping it open.
Quoted 3 lines
I'm going to use spare space to create a new logical volume and move data across and delete the wacky vg-backup unless any other bright ideas arise soon.
Hopefully this will work. I guess you were able to remove an lv previously so you shouldn't have an issue doing this. One thing you didn't answer (and I didn't ask) is if you had problems extending any other lvs. The output of all the tools show the devices in a good state, so to me it just doesn't make sense. Try the lsof bit and see if anything interesting shows up.
Signature · 3 lines
Zac Slade [email protected] ICQ:1415282 YM:krakrjak AIM:ttyp99
Quoted 5 lines · Zac Slade
Quoted 2 lines · Daniel
Guessing the additional info didn't help and there is no easy way to reset the state.
Not really unfortunately.
Feature request :-)
Quoted 2 lines
I have been thinking about this a lot though.
I've never seen it and I'm not sure what the next move really is.
Tough ones.
Quoted 3 lines
Someone
did suggest (and sorry for not posting sooner) that you should run lsof against/dev/mapper/controland see if something is keeping it open.
nothing open.
Quoted 2 lines
Hopefully this will work. I guess you were able to remove an lv previously so you shouldn't have an issue doing this.
Can't remember how I did exactly. I'm sure it was just a lvm learning experience. I should have less problems this time (I'm jinking myself here I'm sure)
Quoted 2 lines
One thing you didn't answer
(and I didn't ask) is if you had problems extending any other lvs.
Didn't try that until just then. Arg - same error.
Quoted 3 lines
The
output of all the tools show the devices in a good state, so to me it just doesn't make sense.
Other suggestions welcome. I'm almost considering a vanilla kernel just to try.
Won't be today though. Need to get an alternate going - filesystem full is a bad error for a backup program. At least I've got twice the space even if I can't extend.
Signature · 2 lines
Daniel Black <[email protected]> Gentoo Crypto/dev-embedded/Forensics/NetMon