LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   Mounting LVM disk when "suspended" (https://www.linuxquestions.org/questions/fedora-35/mounting-lvm-disk-when-suspended-782974/)

ericcarlson 01-18-2010 09:23 AM

Mounting LVM disk when "suspended"
 
I'm trying to mount a volume which pvdisplay reports as "suspended". I also get the message it is "too large for underlying size". This is the point at which I would expect it to mount, but it keeps asking for the file type:

[root@mojo /]# mount /dev/VolGroup00/LogVol00 /mnt
mount: you must specify the filesystem type

Heres the supporting info, any ideas please? Thanks:

[root@mojo /]# lvdisplay
WARNING: Physical Volume /dev/sdb2 is too large for underlying device
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID wNEtIa-jASp-J5Vv-tXQz-OofK-Gf5v-xQWfrh
LV Write Access read/write
LV Status suspended
# open 0
LV Size 147.91 GB
Current LE 4733
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0

--- Logical volume ---
LV Name /dev/VolGroup00/LogVol01
VG Name VolGroup00
LV UUID Gtc7lQ-5ni8-CkiQ-gdSM-2cDF-QNEB-35613j
LV Write Access read/write
LV Status suspended
# open 0
LV Size 1.00 GB
Current LE 32
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:1

--- Logical volume ---
LV Name /dev/vg_mojo/lv_root
VG Name vg_mojo
LV UUID KN9nOB-kvjp-Z43t-ceUx-0Gj9-yiaK-t5ZgTm
LV Write Access read/write
LV Status available
# open 1
LV Size 144.98 GB
Current LE 37114
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:2

--- Logical volume ---
LV Name /dev/vg_mojo/lv_swap
VG Name vg_mojo
LV UUID 6JHs05-EzEl-ZJ44-6wcU-yCUe-XRxL-FGnRQe
LV Write Access read/write
LV Status available
# open 1
LV Size 1.97 GB
Current LE 504
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:3

[root@mojo /]# lvscan
WARNING: Physical Volume /dev/sdb2 is too large for underlying device
ACTIVE '/dev/VolGroup00/LogVol00' [147.91 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.00 GB] inherit
ACTIVE '/dev/vg_mojo/lv_root' [144.98 GB] inherit
ACTIVE '/dev/vg_mojo/lv_swap' [1.97 GB] inherit
[root@mojo /]# pvscan
WARNING: Physical Volume /dev/sdb2 is too large for underlying device
PV /dev/sdb2 VG VolGroup00 lvm2 [148.94 GB / 32.00 MB free]
PV /dev/sda5 VG vg_mojo lvm2 [146.95 GB / 0 free]
Total: 2 [295.88 GB] / in use: 2

[295[root@mojo /]# vgchange -a y
WARNING: Physical Volume /dev/sdb2 is too large for underlying device
device-mapper: resume ioctl failed: Invalid argument
Unable to resume VolGroup00-LogVol00 (253:0)
device-mapper: resume ioctl failed: Invalid argument
Unable to resume VolGroup00-LogVol01 (253:1)
2 logical volume(s) in volume group "VolGroup00" now active
2 logical volume(s) in volume group "vg_mojo" now active
88 GB] / in no VG: 0 [0 ]

[root@mojo /]# mount /dev/VolGroup00/LogVol00 /mnt
mount: you must specify the filesystem type
[root@mojo /]#

smoker 02-13-2010 08:55 AM

Have you tried deactivating the VG then reactivating ?
deactivate :
vgchange -an

activate :
vgchange -ay

device-mapper is complaining "resume ioctl failed: Invalid argument"


All times are GMT -5. The time now is 10:24 AM.